home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
8_7_15.tro
< prev
next >
Wrap
Text File
|
1991-12-22
|
112KB
|
4,283 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright (~c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v'|.5i'
.sp 2P
.LP
\fBRecommendation\ X.419\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBMESSAGE\ HANDLING\ SYSTEMS:\ PROTOCOL\ SPECIFICATIONS\fR
.FS
Recommendation\ X.419 and ISO\ 10021\(hy6 [Information Processing Systems
\(em\ Text Communication \(em MOTIS \(em Protocol Specifications] were
developed in close collaboration and are technically aligned, except for
the differences noted
in Annex\ D.
.FE
.EF '% Fascicle\ VIII.7\ \(em\ Rec.\ X.419''
.OF '''Fascicle\ VIII.7\ \(em\ Rec.\ X.419 %'
.ce 0
.sp 1P
.ce 1000
\fI(Melbourne, 1988)\fR
.sp 9p
.RT
.ce 0
.sp 1P
.PP
The establishment in various countries of telematic services and computer\(hybased
store\(hyand\(hyforward message services in association with
public data networks creates a need to produce standards to facilitate
international message exchange between subscribers to such services.
.sp 1P
.RT
.sp 2P
.LP
The\ CCITT,
.sp 1P
.RT
.sp 1P
.LP
\fIconsidering\fR
.sp 9p
.RT
.PP
(a)
the need for message handling systems;
.PP
(b)
the need to transfer and store messages of different
types;
.PP
(c)
that Recommendation X.200 defines the reference model of open systems interconnection
for CCITT applications;
.PP
(d)
that Recommendations X.208, X.217, X.218 and X.219
provide the foundation for CCITT applications;
.PP
(e)
that the X.500\(hyseries Recommendations define directory systems;
.PP
(
f
)
that message handling systems are defined in a series of Recommendations:
X.400, X.402, X.403, X.407, X.408, X.411, X.413 and X.419; and
.PP
(g)
that interpersonal messaging is defined in
Recommendations\ X.420 and T.330;
.sp 1P
.LP
\fIunanimously declares\fR
.sp 9p
.RT
.PP
(1)
that the protocol for accessing the message transfer
system (the MTS access protocol\ \(em\ P3) is defined in Section\ 2;
.PP
(2)
that the protocol for accessing a message store (the MS access protocol\
\(em\ P7) is also defined in Section\ 2;
.PP
(3)
that the protocol used between message transfer agents (MTAs) to provide
for the distributed operation of the message transfer system (the MTS transfer
protocol\ \(em\ P1) is defined in Section\ 3.
\v'6p'
.sp 1P
.ce 1000
TABLE\ OF\ CONTENTS
.ce 0
.sp 1P
.LP
Section\ 1\ \(em
\fIIntroduction\fR
.sp 1P
.RT
.sp 2P
.LP
0
Introduction
.sp 1P
.RT
.sp 1P
.LP
1
Scope
.sp 9p
.RT
.sp 1P
.LP
2
References
.sp 9p
.RT
.sp 1P
.LP
3
Definitions
.sp 9p
.RT
.sp 1P
.LP
4
Abbreviations
.sp 9p
.RT
.sp 1P
.LP
5
Conventions
.sp 9p
.RT
.LP
.sp 1
.bp
.sp 2P
.LP
Section\ 2\ \(em
\fIMessage handling system access protocol specifications\fR
.sp 1P
.RT
.sp 1P
.LP
6
Overview of the MHS access protocols
.sp 9p
.RT
.sp 1P
.LP
7
MTS access protocol abstract syntax definition
.sp 9p
.RT
.sp 1P
.LP
8
MS access protocol abstract syntax definition
.sp 9p
.RT
.sp 1P
.LP
9
Mapping onto used services
.sp 9p
.RT
.sp 1P
.LP
10
Conformance
.sp 9p
.RT
.sp 2P
.LP
Section\ 3\ \(em
\fIMessage transfer system transfer protocol specification\fR
.sp 1P
.RT
.sp 1P
.LP
11
Overview of the MTS transfer protocol
.sp 9p
.RT
.sp 1P
.LP
12
MTS transfer protocol abstract syntax definition
.sp 9p
.RT
.sp 1P
.LP
13
Mapping onto used services
.sp 9p
.RT
.sp 1P
.LP
14
Conformance
.sp 9p
.RT
.sp 1P
.LP
\fIAnnex\ A\fR \(em
Reference definition of MHS protocol object identifiers
.sp 9p
.RT
.LP
\fIAnnex\ B\fR \(em
Interworking with 1984 systems
.LP
\fIAnnex\ C\fR \(em
Differences between 1984 and 1988 MHS protocols
.LP
\fIAnnex\ D\fR \(em
Differences between ISO and CCITT versions
.LP
.rs
.sp 25P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
SECTION\ 1\ \(em
INTRODUCTION
.sp 1P
.RT
.sp 2P
.LP
\fB0\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
This Recommendation is one of a set of Recommendations defining
message handling in a distributed open systems environment.
.PP
Message handling provides for the exchange of messages between users on
a store\(hyand\(hyforward basis. A message submitted by one user (the
\fIoriginator\fR ) is transferred through the message transfer system (MTS) and
delivered to one or more other users (the \fIrecipients\fR ). A user may
interact
directly with the MTS, or indirectly via a message store (MS).
.PP
The MTS comprises a number of message\(hytransfer\(hyagents (MTAs), which
transfer messages and deliver them to their intended recipients.
.PP
This Recommendation was developed jointly by CCITT and ISO. The
equivalent ISO document is ISO\ 10021\(hy6.
.RT
.sp 2P
.LP
\fB1\fR \fBScope\fR
.sp 1P
.RT
.PP
This Recommendation specifies the MTS access protocol (P3) used
between a remote user\(hyagent and the MTS to provide access to the MTS
abstract service defined in Recommendation\ X.411.
.PP
This Recommendation also specifies the MS access protocol (P7) used
between a remote user\(hyagent and a message\(hystore (MS) to provide access
to the MS abstract service defined in Recommendation\ X.413.
.PP
This Recommendation also specifies the MTS transfer protocol (P1) used
between MTASs to provide the distributed operation of the MTS as defined
in
Recommendation\ X.411.
.PP
Recommendation X.402 identifies the other Recommendations which define
other aspects of message handling systems.
.PP
Section 2 of this Recommendation specifies the MHS access protocols
(P3 and P7). Paragraph\ 6 provides an overview of the MHS access protocols.
Paragraph\ 7 defines the abstract\(hysyntax of the MTS access protocol (P3).
Paragraph\ 8 defines the abstract\(hysyntax of the MS access protocol (P7).
Paragraph\ 9 defines the mapping of the MHS access protocols onto used
services. Paragraph\ 10 specifies conformance requirements for systems
implementing the
MHS access protocols.
.PP
Section 3 of this Recommendation specifies the MTS transfer
protocol (P1). Paragraph\ 11 provides an overview of the MTS transfer protocol
(P1). Paragraph\ 12 defines the abstract\(hysyntax of the MTS transfer
protocol
(P1). Paragraph\ 13 defines the mapping of the MTS transfer protocol (P1)
onto used services. Paragraph\ 14 specifies conformance requirements for
systems
implementing the MTS transfer protocol (P1).
.PP
Annex A provides a reference definition of the MHS protocol object
identifiers cited in the ASN.1 modules in the body of this Recommendation.
.PP
Annex B describes protocol rules for interworking with implementations
of the Recommendation\ X.411 (1984) using the MTS Transfer Protocol (P1).
.PP
Annex C identifies the differences between the Recommendation X.411
(1984) and this Recommendation.
.PP
Annex D identifies the technical differences between the ISO and CCITT
versions of CCITT Recommendations\ X.419 and ISO\ 10021\(hy6.
.RT
.sp 2P
.LP
\fB2\fR \fBReferences\fR
.sp 1P
.RT
.PP
References are listed in Recommendation X.402.
.RT
.sp 2P
.LP
\fB3\fR \fBDefinitions\fR
.sp 1P
.RT
.PP
Definitions are given in Recommendation X.402.
.RT
.sp 2P
.LP
\fB4\fR \fBAbbreviations\fR
.sp 1P
.RT
.PP
Abbreviations are listed in Recommendation X.402.
.bp
.RT
.sp 2P
.LP
\fB5\fR \fBConventions\fR
.sp 1P
.RT
.PP
This Recommendation uses the descriptive conventions described
below.
.RT
.sp 1P
.LP
5.1
\fITerms\fR
.sp 9p
.RT
.PP
Throughout this Recommendation the words of defined terms, and the names
and values of service parameters and protocol fields, unless they are
proper names, begin with a lower\(hycase letter and are linked by a hyphen
thus: defined\(hyterms. Proper names begin with an upper\(hycase letter
and are not linked by a hyphen thus: Proper Name.
.RT
.sp 1P
.LP
5.2
\fIAbstract syntax definitions\fR
.sp 9p
.RT
.PP
This Recommendation defines the abstract\(hysyntax of the MHS
protocols using the abstract syntax notation (ASN.1) defined in
Recommendation\ X.208 and the remote operations notation defined in
Recommendation\ X.219.
.RT
.LP
.rs
.sp 40P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
SECTION\ 2\ \(em
MESSAGE\ HANDLING\ SYSTEM\ ACCESS\ PROTOCOL\ SPECIFICATIONS
.sp 1P
.RT
.sp 2P
.LP
\fB6\fR \fBOverview of the MHS access protocols\fR
.sp 1P
.RT
.sp 1P
.LP
6.1
\fIMHS access protocol model\fR
.sp 9p
.RT
.PP
Paragraph 6 of Recommendation X.411 describes an abstract model of the
message transfer system (MTS), and the MTS abstract service which it
provides to its MTS\(hyusers.
.PP
Paragraph 6 of Recommendation X.413 describes an abstract model of a message
store (MS), and the MTS abstract service which it provides to its
MS\(hyusers.
.PP
This paragraph describes how the MTS abstract service and the MS
abstract service are supported by instances of OSI communication when an
abstract\(hyservice user and an abstract\(hyservice provider are realized as
application\(hyprocesses located in different open systems.
.PP
In the OSI environment, communication between application\(hyprocesses
is represented in terms of communication between a pair of application\(hyentities
(AEs) using the presentation\(hyservice. The functionality of an
application\(hyentity is factored into a set of one or more
application\(hyservice\(hyelements (ASEs). The interaction between AEs
is described in terms of their use of the services provided by the ASEs.
.PP
Access to the MTS abstract service is supported by three
application\(hyservice\(hyelements, each supporting a type of port paired
between an MTS\(hyuser and the MTS in the abstract model. The message submission
service
element (MSSE) supports the services of the submission\(hyport; the message
delivery service element (MDSE) supports the services of the delivery\(hyport;
and the message administration service element (MASE) supports the services
of the administration\(hyport. The MSSE, MDSE and MASE are asymmetric\(hyASEs;
that is, the MTS\(hyuser ASEs act as the consumer, and the MTS ASEs act
as the supplier, of the MTS abstract service.
.PP
Similarly, access to the MS abstract service is supported by three
application\(hyservice\(hyelements: the message submission service element
(MSSE)
supports the indirect\(hysubmission\(hyport; the message retrieval service
element
(MRSE) supports the services of the retrieval\(hyport; and the message
administration service element (MASE) supports the services of the
administration\(hyport. The MS\(hyuser ASEs act as the consumer, and the
MS ASEs act as the supplier, of the MS abstract service.
.PP
These application\(hyservice\(hyelements are in turn supported by other
application\(hyservice\(hyelements.
.PP
The remote operations service element (ROSE) supports the
request/reply paradigm of the abstract operations that occur at the ports in
the abstract model. The MSSE, MDSE, MRSE and MASE provide the mapping function
of the abstract\(hysyntax notation of an abstract\(hyservice onto the services
provided by the ROSE.
.PP
Optionally, the reliable transfer service element (RTSE) may be used to
reliably transfer the application\(hyprotocol\(hydata\(hyunits (APDUs)
that contain the parameters of the operations between AEs.
.PP
The association control service element (ACSE) supports the
establishment and release of an application\(hyassociation between a pair
of AEs. Associations between an MTS\(hyuser and the MTS may be established
by either the MTS\(hyuser or the MTS. Associations between an MS\(hyuser
and an MS may be
established only by the MS\(hyuser. Only the initiator of an established
association can release it.
.PP
The combination of one or more of the MSSE, MDSE, MRSE and MASE,
together with their supporting ASEs, defines the application\(hycontext of an
application\(hyassociation. Note that a single application\(hyassociation
may be used to support one or more types paired between two objects in
the abstract model.
.PP
Table 1/X.419 identifies the application\(hycontexts defined in this
Recommendation for the MTS access protocol and MS access protocol.
.RT
.PP
If the MTS access protocol (P3) is supported, then support for the \fBmts\(hyaccess\fR
and \fBmts\(hyforced\(hyaccess\fR application\(hycontexts is mandatory
for an \fBMTA\fR . If an MTA supports the \fBmts\(hyreliable\(hyaccess\fR
application\(hycontext, it
shall also support the \fBmts\(hyforced\(hyreliable\(hyaccess\fR , and
vice versa. Support
for each of the MTS access protocol (P3) application\(hycontext is optional
for an MTS\(hyuser.
.PP
If the MS access protocol (P7) is supported, then support for the
\fBms\(hyaccess\fR application\(hycontext is mandatory for an MS, and support
for the
\fBms\(hyreliable\(hyaccess\fR application\(hycontext is optional. Support
for each of the MS access protocol (P7) application\(hycontexts is optional
for an MS\(hyuser.
.PP
Figure 1/X.419 models an application\(hycontext between an MTS\(hyuser
and the MTS. The consumer role of the MTS\(hyuser ASEs, and the supplier
role of the MTS ASEs, is indicated by a subscripted\ \*Qc\*U or \*Qs\*U,
respectively.
.PP
Similarly, Figure 2/X.419 models an application\(hycontext between an
MS\(hyuser and the MS.
.bp
.RT
.ce
\fBH.T. [T1.419]\fR
.ce
TABLE\ 1/X.419
.ce
\fBMHS access protocol application contexts\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(72p) | cw(18p) sw(18p) sw(18p) sw(18p) | cw(18p) sw(18p) sw(18p) , ^ | c | c | c | c | c | c | c.
Application context Message Handling ASEs Supporting ASEs
MSSE MDSE MRSE MASE ROSE RTSE ACSE
_
.T&
lw(72p) | lw(18p) | lw(18p) | lw(18p) | lw(18p) | lw(18p) | lw(18p) | lw(18p) .
\fIMTS access protocol\fR
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
mts\(hyaccess C C \(em C X \(em X
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
mts\(hyforced\(hyaccess S S \(em S X \(em X
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
mts\(hyreliable\(hyaccess C C \(em C X X X
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
T{
mts\(hyforced\(hyreliable\(hyaccess
T} S S \(em S X X X
_
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
\fIMS access protocol\fR
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
ms\(hyaccess C \(em C C X \(em X
.T&
lw(72p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) | cw(18p) .
ms\(hyreliable\(hyaccess C \(em C C X X T{
X
X present
.parag
\(em absent
.parag
C present with initiator the consumer
.parag
S present with initiator the supplier
.parag
T}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau 1/X.419 [T1.419], p.1\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.rs
.sp 22P
.ad r
\fBFigure 1/X.419, p.2\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 22P
.ad r
\fBFigure 2/X.419, p.3\fR
.sp 1P
.RT
.ad b
.RT
.LP
\fR
.sp 1P
.LP
6.2
\fIServices provided by the MTS access protocol\fR
.sp 9p
.RT
.PP
The MTS access protocol (P3) comprises the following operations
which provide the services defined in Recommendation\ X.411:
.RT
.LP
\fIMTS\(hybind and MTS\(hyunbind\fR
.LP
a)
MTS\(hybind
.LP
b)
MTS\(hyunbind\fR
.LP
\fIMessage submission service element (MSSE)\fR
.LP
c)
message\(hysubmission
.LP
d)
probe\(hysubmission
.LP
e)
cancel\(hydeferred\(hydelivery
.LP
f
)
submission\(hycontrol
.LP
\fIMessage delivery service element (MDSE)\fR
.LP
g)
message\(hydelivery
.LP
h)
report\(hydelivery
.LP
i)
delivery\(hycontrol
.LP
\fIMessage administration service element (MASE)\fR
.LP
j
)
register
.LP
k)
change\(hycredentials.
.sp 1P
.LP
6.3
\fIServices provided by the MS access protocol\fR
.sp 9p
.RT
.PP
The MS access protocol (P7) comprises the following operations
which provide the services defined in Recommendation\ X.413:
.RT
.LP
\fIMS\(hybind and MS\(hyunbind\fR
.LP
a)
MS\(hybind
.LP
b)
MS\(hyunbind\fR .bp
.LP
\fIMessage submission service element (MSSE)\fR
.LP
c)
message\(hysubmission
.LP
d)
probe\(hysubmission
.LP
e)
cancel\(hydeferred\(hydelivery
.LP
f
)
submission\(hycontrol
.LP
\fIMessage retrieval service element (MRSE)\fR
.LP
g)
summarize
.LP
h)
list
.LP
i)
fetch
.LP
j
)
delete
.LP
k)
register\(hyMS
.LP
l)
alert
.LP
\fIMessage administration service element (MASE)\fR
.LP
m)
register
.LP
n)
change\(hycredentials.
.sp 1P
.LP
6.4
\fIUse of underlying services\fR
.sp 9p
.RT
.PP
The MHS access protocols make use of underlying services as
described below.
.RT
.sp 1P
.LP
6.4.1
\fIUse of \fR \fIROSE services\fR
.sp 9p
.RT
.PP
The remote operations service element (ROSE) is defined in
Recommendation\ X.219.
.PP
The ROSE supports the request/reply paradigm of remote operations.
.PP
The MSSE, MDSE, MRSE and MASE are the sole users of the RO\(hyINVOKE,
RO\(hyRESULT, RO\(hyERROR, RO\(hyREJECT\(hyU and RO\(hyREJECT\(hyP services
of the ROSE.
.PP
The remote operations of the MTS access protocol (P3) and the MS
access protocol (P7) are Class\ 2 (asynchronous) operations.
.RT
.sp 1P
.LP
6.4.2
\fIUse of \fR \fIRTSE services\fR
.sp 9p
.RT
.PP
The reliable transfer service element (RTSE) is defined in
Recommendation\ X.218.
.PP
The RTSE provides for the reliable transfer of
application\(hyprotocol\(hydata units (APDUs). The RTSE ensures that each
APDU is
completely transferred exactly once, or that the sender is warned of an
exception. The RTSE recovers from communication and end\(hysystem failure and
minimizes the amount of retransmission needed for recovery.
.PP
Alternative application\(hycontexts with and without RTSE are defined to
support the MHS access protocols.
.PP
The RTSE is used in the normal mode. The use of the normal mode of the
RTSE implies the use of the normal mode of the ACSE and the normal mode
of the presentation\(hyservice.
.PP
If the RTSE is included in an application\(hycontext, the MHS access
protocol MTS\(hybind and MTS\(hyunbind (or MS\(hybind and MS\(hyunbind)
are the sole users of the RT\(hyOPEN and RT\(hyCLOSE services of the RTSE.
The ROSE is the sole user of the RT\(hyTRANSFER, RT\(hyTURN\(hyPLEASE,
RT\(hyTURN\(hyGIVE, RT\(hyP\(hyABORT and RT\(hyU\(hyABORT
services of the RTSE.
.RT
.sp 1P
.LP
6.4.3
\fIUse of \fR \fIACSE services\fR
.sp 9p
.RT
.PP
The association control service element (ACSE) is defined in
Recommendation\ X.217.
.PP
The ACSE provides for the control (establishment, release, abort) of application\(hyassociations
between AEs.
.PP
If the RTSE is not included in an application\(hycontext, the MHS access
protocol MTS\(hybind and MTS\(hyunbind (or MS\(hybind and MS\(hyunbind)
are the sole users of the A\(hyASSOCIATE and A\(hyRELEASE services of the
ACSE in normal mode. The ROSE is the user of the A\(hyABORT and A\(hyP\(hyABORT
services of the ACSE.
.PP
If the RTSE is included in an application\(hycontext, the RTSE is the
sole user of the A\(hyASSOCIATE, A\(hyRELEASE, A\(hyABORT and A\(hyP\(hyABORT
services of
the ACSE. The use of the normal mode of the RTSE implies the use of the
normal mode of the ACSE and the normal mode of the presentation\(hyservice.
.bp
.RT
.sp 1P
.LP
6.4.4
\fIUse of the \fR \fIpresentation\(hyservice\fR
.sp 9p
.RT
.PP
The presentation\(hyservice is defined in Recommendation X.216.
.PP
The presentation layer coordinates the representation (syntax) of the application
layer semantics that are to be exchanged.
.PP
In normal mode, a different presentation\(hycontext is used for each
abstract\(hysyntax included in the application\(hycontext.
.PP
The ACSE is the sole user of the P\(hyCONNECT, P\(hyRELEASE, P\(hyU\(hyABORT
and P\(hyP\(hyABORT services of the presentation\(hyservice.
.PP
If the RTSE is not included in the application\(hycontext, the ROSE is
the sole user of the P\(hyDATA service of the presentation\(hyservice.
.PP
If the RTSE is included in the application\(hycontext, the RTSE is the
sole user of the
.PP
P\(hyACTIVITY\(hySTART, P\(hyDATA, P\(hyMINOR\(hySYNCHRONIZE, P\(hyACTIVITY\(hyEND,
P\(hyACTIVITY\(hyINTERRUPT,
.PP
P\(hyACTIVITY\(hyDISCARD, P\(hyU\(hyEXCEPTION\(hyREPORT, P\(hyACTIVITY\(hyRESUME,
P\(hyP\(hyEXCEPTION\(hyREPORT,
.PP
P\(hyTOKEN\(hyPLEASE and P\(hyCONTROL\(hyGIVE services of the presentation\(hyservice.
The use of the normal mode of the
RTSE implies the use of the normal mode of the ACSE and the normal mode
of the presentation\(hyservice.
.RT
.sp 1P
.LP
6.4.5
\fIUse of lower layer services\fR
.sp 9p
.RT
.PP
The session\(hyservice is defined in Recommendation X.215. The
session layer structures the dialogue of the flow of information between the
end\(hysystems.
.PP
If the RTSE is included in the application\(hyassociation, the kernel,
half\(hyduplex, exceptions, minor\(hysynchronize and activity\(hymanagement
functional units of the session\(hyservice are used by the presentation layer.
.PP
If the RTSE is not included in the application\(hyassociation, the kernal
and duplex functional units of the session\(hyservice are used by the presentation
layer.
.PP
The transport\(hyservice is defined in Recommendation X.214. The
transport layer provides for the end\(hyto\(hyend transparent transfer
of data over the underlying network connection.
.PP
The choice of the class of transport\(hyservice used by the session layer
depends on the requiements for multiplexing and error recovery. Support
for
transport class\ 0 (non\(hymultiplexing) is mandatory. Transport expedited
service is not used.
.PP
Support for other classes is optional. A multiplexing class may be
used to multiplex an MHS access protocol and other access protocols (e.g.\
the directory access protocol (DAP) defined in Recommendation\ X.519) over
the same network connection. An error recovery class may be chosen if the
RTSE is
omitted from an application\(hycontext over a network connection with an
unacceptable residual error rate.
.PP
An underlying network supporting the OSI network\(hyservice defined in
Recommendation\ X.213 is assumed.
.PP
A network\(hyaddress is as defined in Recommendation X.121,
Recommendations\ E.163/E.164, or Recommendation\ X.200 (OSI\ NSAP\(hyaddress).
.RT
.sp 2P
.LP
\fB7\fR \fBMTS access protocol abstract syntax definition\fR
.sp 1P
.RT
.PP
The abstract\(hysyntax of the MTS access protocol (P3) is defined in Figure\
3/X.419.
.PP
The abstract\(hysyntax of the MTS access protocol (P3) is defined using
the abstract\(hysyntax notation (ASN.1) defined in Recommendation\ X.208,
and the remote operations notation defined in Recommendation\ X.219.
.PP
The abstract\(hysyntax definition of the MTS access protocol (P3) has the
following major parts:
.RT
.LP
\(em
\fIPrologue:\fR \| declarations of the exports from, and imports
to, the MTS Access Protocol (P3) module (Figure\ 3/X.419, Part\ 1).
.LP
\(em
\fIApplication contexts:\fR \| definitions of application\(hycontexts
that may be used between an MTS\(hyuser and the MTS (Figure\ 3/X.419, Parts\
2
and\ 3).
.LP
\(em
\fIMessage submission service element:\fR \| definitions of the
message submission service element (MSSE) and its remote operations and
errors (Figure\ 3/X.419, Part\ 4).
.LP
\(em
\fIMessage delivery service element:\fR \| definitions of the
message delivery service element (MDSE) and its remote operations and errors
(Figure\ 3/X.419, Part\ 5).
.LP
\(em
\fIMessage administration service element:\fR \| definitions of the message
administration service element (MSSE) and its remote operations and
errors (Figure\ 3/X.419, Part\ 6).
.bp
.LP
MTSAccessProtocol {\|joint\(hyiso\(hyccitt mhs\(hymotis(6) protocols(0)
modules(0)
mts\(hyaccess\(hyprotocol(1)\|}
.LP
DEFINITIONS IMPLICIT TAGS ::=
.LP
BEGIN
.LP
.sp 2
\(hy\(hy\ \fIPrologue\fR
.LP
EXPORTS
.LP
\(hy\(hy\ \fIApplication service elements\fR
.LP
mSSE, mDSE, mASE;
.LP
IMPORTS
.LP
\(hy\(hy\ \fIApplication service elements and application contexts\fR
.LP
APPLICATION\(hySERVICE\(hyELEMENT, APPLICATION\(hyCONTEXT, aCSE
.LP
FROM Remote\(hyOperations\(hyNotation\(hyextension {\|joint\(hyiso\(hyccitt
remote\(hyoperations(4)
.LP
\ \ notation\(hyextension(2)\|}
.LP
rTSE
.LP
FROM Reliable\(hyTransfer\(hyAPDUs {\|joint\(hyiso\(hyccitt
reliable\(hytransfer(3) apdus(0)\|}
.LP
\(hy\(hy\ \fIMTS abstract service parameters\fR
.LP
MTSBind, MTSUnbind, MessageSubmission, ProbeSubmission,
CancelDeferredDelivery,
.LP
SubmissionControl, MessageDelivery, ReportDelivery,
DeliveryControl, Register,
.LP
ChangeCredentials, SubmissionControlViolated,
ElementOfServiceNotSubscribed,
.LP
DeferredDeliveryCancellationRejected, OriginatorInvalid,
RecipientImproperlySpecified,
.LP
MessageSubmissionIdentifierInvalid, InconsistentRequest,
SecurityError,
.LP
UnsupportedCriticalFunction, RemoteBindError,
DeliveryControlViolated, ControlViolatesRegistration,
.LP
RegisterRejected, NewCredentialsUnacceptable,
OldCredentialsIncorrectlySpecified
.LP
FROM MTSAbstractService {\|joint\(hyiso\(hyccitt mhs\(hymotis(6) mts(3)
modules(0)
.LP
\ \ mts\(hyabstract\(hyservice(1)^}
.LP
\(hy\(hy\ \fIObject identifiers\fR
.LP
id\(hyac\(hymts\(hyaccess, id\(hyac\(hymts\(hyforced\(hyaccess,
id\(hyac\(hymts\(hyreliable\(hyaccess, id\(hyac\(hymts\(hyforced\(hyreliable\(hyaccess,
.LP
id\(hyas\(hyacse, id\(hyas\(hymsse, id\(hyas\(hymdse, id\(hyas\(hymrse,
id\(hyas\(hymase,
id\(hyas\(hymts, id\(hyas\(hymts\(hyrtse,
.LP
id\(hyase\(hymsse, id\(hyase\(hymdse, id\(hyase\(hymase
.LP
FROM MHSProtocolObjectIdentifiers {\|joint\(hyiso\(hyccitt
mhs\(hymotis(6) protocols(0)
.LP
\ \ modules(0) object\(hyidentifiers(0)\|};
.ce 1000
FIGURE\ 3/X.419\ (Part 1 of 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIApplication contexts omitting RTSE\fR
.LP
\(hy\(hy\ \fIMTS\(hyuser initiated\fR
.LP
mts\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE\|}
.LP
BIND MTSBind
.LP
UNBIND MTSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
INITIATOR CONSUMER OF {\|mSSE, mDSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymdse,
\(hy\(hy\ of MDSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hymts
\(hy\(hy\ of MTSBind and MTSUnbind\|\(hy\(hy\|}
.LP
::= id\(hyac\(hymts\(hyaccess
.LP
.sp 2
\(hy\(hy\ \fIMTS initiated\fR
.LP
mts\(hyforced\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE\|}
.LP
BIND MTSBind
.LP
UNBIND MTSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
RESPONDER CONSUMER OF {\|mSSE, mDSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymdse,
\(hy\(hy\ of MDSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hymts
\(hy\(hy\ of MTSBind and MTSUnbind\|\(hy\(hy\|}
.LP
::= id\(hyac\(hymts\(hyforced\(hyaccess
.ce 1000
FIGURE\ 3/X.419\ (Part 2 to 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIApplication contexts including RTSE in normal mode\fR
.LP
\(hy\(hy\ \fIMTS\(hyuser initiated\fR
.LP
mts\(hyreliable\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE, rTSE\|}
.LP
BIND MTSBind
.LP
UNBIND MTSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
INITIATOR CONSUMER OF {\|mSSE, mDSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymdse,
\(hy\(hy\ of MDSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hymts\(hyrtse
\(hy\(hy\ of MTSBind and MTSUnbind, including
RTSE\|\(hy\(hy\|}
.LP
::= id\(hyac\(hymts\(hyreliable\(hyaccess
.LP
.sp 2
\(hy\(hy\ \fIMTS initiated\fR
.LP
mts\(hyforced\(hyreliable\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE, rTSE\|}
.LP
BIND MTSBind
.LP
UNBIND MTSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
RESPONDER CONSUMER OF {\|mSSE, mDSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymdse,
\(hy\(hy\ of MDSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hymts\(hyrtse
\(hy\(hy\ of MTSBind and MTSUnbind, including
RTSE\|\(hy\(hy\|}
.LP
::= id\(hyac\(hymts\(hyforced\(hyreliable\(hyaccess
.ce 1000
FIGURE\ 3/X.419\ (Part 3 of 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIMessage submission service element\fR
.LP
mSSE APPLICATION\(hySERVICE\(hyELEMENT
.LP
CONSUMER INVOKES\|{
.LP
message\(hysubmission,
.LP
probe\(hysubmission,
.LP
cancel\(hydeferred\(hydelivery\|}
.LP
SUPPLIER INVOKES\|{
.LP
submission\(hycontrol\|}
.LP
::= id\(hyase\(hymsse
.LP
.sp 2
\(hy\(hy\ \fIRemote operations\fR
.LP
message\(hysubmission MessageSubmission ::= 3
.LP
probe\(hysubmission ProbeSubmission ::= 4
.LP
cancel\(hydeferred\(hydelivery CancelDeferredDelivery ::= 7
.LP
submission\(hycontrol SubmissionControl ::= 2
.LP
.sp 2
.LP
\(hy\(hy\ \fIRemote errors\fR
.LP
submission\(hycontrol\(hyviolated SubmissionControlViolated ::= 1
.LP
element\(hyof\(hyservice\(hynot\(hysubscribed ElementOfServiceNotSubscribed
::= 4
.LP
deferred\(hydelivery\(hycancellation\(hyrejected DeferredDeliveryCancellationRejected
::= 8
.LP
originator\(hyinvalid OriginatorInvalid ::= 2
.LP
recipient\(hyimproperly\(hyspecified RecipientImproperlySpecified ::= 3
.LP
message\(hysubmission\(hyidentifier\(hyinvalid MessageSubmissionIdentifierInvalid
::= 7
.LP
inconsistent\(hyrequest InconsistentRequest ::= 11
.LP
security\(hyerror SecurityError ::= 12
.LP
unsupported\(hycritical\(hyfunction UnsupportedCriticalFunction ::= 13
.LP
remote\(hybind\(hyerror RemoteBindError ::= 15
.ce 1000
FIGURE\ 3/X.419\ (Part 4 of 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIMessage delivery service element\fR
.LP
mDSE APPLICATION\(hySERVICE\(hyELEMENT
.LP
CONSUMER INVOKES\|{
.LP
delivery\(hycontrol}
.LP
SUPPLIER INVOKES\|{
.LP
message\(hydelivery,
.LP
report\(hydelivery\|}
.LP
::= id\(hyase\(hymdse
.LP
.sp 2
\(hy\(hy\ \fIRemote operations\fR
.LP
message\(hydelivery MessageDelivery ::= 5
.LP
report\(hydelivery ReportDelivery ::= 6
.LP
delivery\(hycontrol DeliveryControl ::= 2
.LP
.sp 2
.LP
\(hy\(hy\ \fIRemote errors\fR
.LP
delivery\(hycontrol\(hyviolated DeliveryControlViolated ::= 1
.LP
control\(hyviolates\(hyregistration ControlViolatesRegistration ::= 14
.LP
.sp 2
\(hy\(hy\ security\(hyerror ::= 12, defined in Part 4
.LP
\(hy\(hy\ unsupported\(hycritical\(hyfunction ::= 13, defined in Part 4
.ce 1000
FIGURE\ 3/X.419\ (Part 5 of 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIMessage administration service element\fR
.LP
mASE APPLICATION\(hySERVICE\(hyELEMENT
.LP
CONSUMER INVOKES\|{
.LP
register,
.LP
change\(hycredentials\|}
.LP
SUPPLIER INVOKES\|{
.LP
change\(hycredentials\|}
.LP
::= id\(hyase\(hymase
.LP
.sp 2
\(hy\(hy\ \fIRemote operations\fR
.LP
register Register ::= 1
.LP
change\(hycredentials ChangeCredentials ::= 8
.LP
.sp 2
\(hy\(hy\ \fIRemote errors\fR
.LP
register\(hyrejected RegisterRejected ::= 10
.LP
new\(hycredentials\(hyunacceptable NewCredentialsUnacceptable ::= 6
.LP
old\(hycredentials\(hyincorrectly\(hyspecified OldCredentialsIncorrectlySpecified
::= 5
.LP
.sp 2
.LP
END\ \(hy\(hy\ of \fIMTSAccessProtocol\fR
.ce 1000
FIGURE\ 3/X.419\ (Part 6 of 6)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS access protocol (P3)\fR
.ce 0
.sp 1P
.LP
.sp 6
.sp 2P
.LP
\fB8\fR \fBMS access protocol abstract syntax definition\fR
.sp 1P
.RT
.PP
The abstract\(hysyntax of the MS access protocol (P7) is defined in
Figure\ 4/X.419.
.PP
The abstract\(hysyntax of the MS access protocol (P7) is defined using
the abstract syntax notation (ASN.1) defined in Recommendation\ X.208,
and the remote operations notation defined in Recommendation\ X.219.
.PP
The abstract\(hysyntax definition of the MS access protocol (P7) has the
following major parts:
.RT
.LP
\(em
\fIPrologue:\fR \| declarations of the exports from, and imports
to, the MTS access protocol (P3) module (Figure\ 4/X.419, Part\ 1).
.LP
\(em
\fIApplication contexts:\fR \| definitions of application\(hycontexts
that may be used between an MS\(hyuser and the MS (Figure\ 4/X.419, Part\
2).
.LP
\(em
\fIMessage retrieval service element:\fR \| definitions of the
message retrieval service element (MRSE) and its remote operations and
errors (Figure\ 4/X.419, Parts\ 3 and\ 4).
.LP
.bp
.LP
MSAccessProtocol {\|joint\(hyiso\(hyccitt mhs\(hymotis(6) protocols(0)
modules(0)
ms\(hyaccess\(hyprotocol(2)\|}
.LP
DEFINITIONS IMPLICIT TAGS ::=
.LP
BEGIN
.LP
.sp 2
\(hy\(hy\ \fIPrologue\fR
.LP
EXPORTS
.LP
mRSE;
.LP
IMPORTS
.LP
\(hy\(hy\ \fIApplication service elements and application contexts\fR
.LP
APPLICATION\(hySERVICE\(hyELEMENT, APPLICATION\(hyCONTEXT, aCSE
.LP
FROM Remote\(hyOperations\(hyNotation\(hyextension {\|joint\(hyiso\(hyccitt
remote\(hyoperations(4)
.LP
\ \ notation\(hyextension(2)\|}
.LP
rTSE
.LP
FROM Reliable\(hyTransfer\(hyAPDUs {\|joint\(hyiso\(hyccitt
reliable\(hytransfer(3) apdus(0)\|}
.LP
mSSE, mASE
.LP
FROM MTSAccessProtocol
{\|joint\(hyiso\(hyccitt mhs\(hymotis(6) protocols(0)
.LP
modules(0) mts\(hyaccess\(hyprotocol(1)}
.LP
\(hy\(hy\ \fIMS abstract service parameters\fR
.LP
MSBind, MSUnbind, Summarize, List, Fetch, Delete, Register\(hyMS,
Alert, AttributeError,
.LP
AutoActionRequestError, DeleteError, FetchRestrictionError,
RangeError, SecurityError,
.LP
ServiceError, SequenceNumberError
.LP
FROM MSAbstractService {\|joint\(hyiso\(hyccitt mhs\(hymotis(6) ms(4)
modules(0)
.LP
\ \ abstract\(hyservice(1)^}
.LP
\(hy\(hy\ \fIObject identifiers\fR
.LP
id\(hyac\(hyms\(hyaccess, id\(hyac\(hyms\(hyreliable\(hyaccess, id\(hyas\(hyacse,
id\(hyas\(hymsse,
id\(hyas\(hymrse, id\(hyas\(hymase, id\(hyas\(hyms, id\(hyas\(hyms\(hyrtse,
id\(hyase\(hymrse
.LP
FROM MHSProtocolObjectIdentifiers {\|joint\(hyiso\(hyccitt
mhs\(hymotis(6) protocols(0)
.LP
\ \ modules(0) object\(hyidentifiers(0)\|};
.ce 1000
FIGURE\ 4/X.419\ (Part 1 of 4)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MS access protocol (P7)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIApplication context omitting RTSE\fR
.LP
ms\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE\|}
.LP
BIND MSBind
.LP
UNBIND MSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
INITIATOR CONSUMER OF {\|mSSE, mRSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymrse,
\(hy\(hy\ of MRSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hyms
\(hy\(hy\ of MSBind and MSUnbind\|\(hy\(hy\|}
.LP
::= id\(hyac\(hyms\(hyaccess
.LP
.sp 2
\(hy\(hy\ \fIApp;ication context including RTSE\fR
.LP
ms\(hyreliable\(hyaccess APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE, rTSE\|}
.LP
BIND MSBind
.LP
UNBIND MSUnbind
.LP
REMOTE OPERATIONS {\|rOSE\|}
.LP
INITIATOR CONSUMER OF {\|mSSE, mRSE, mASE\|}
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymsse,
\(hy\(hy\ of MSSE, including ROSE
.LP
id\(hyas\(hymrse,
\(hy\(hy\ of MRSE, including ROSE
.LP
id\(hyas\(hymase,
\(hy\(hy\ of MASE, including ROSE
.LP
id\(hyas\(hyms\(hyrtse
\(hy\(hy\ of MSBind and MSUnbind, including
RTSE\|\(hy\(hy\|}
.LP
::= id\(hyac\(hyms\(hyreliable\(hyaccess
.ce 1000
FIGURE\ 4/X.419\ (Part 2 of 4)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MS access protocol (P7)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIMessage retrieval service element\fR
.LP
mRSE APPLICATION\(hySERVICE\(hyELEMENT
.LP
CONSUMER INVOKES\|{
.LP
summarize,
.LP
list,
.LP
fetch,
.LP
delete,
.LP
register\(hyMS,\|}
.LP
SUPPLIER INVOKES\|{
.LP
alert\|}
.LP
::= id\(hyase\(hymrse
.LP
.sp 2
\(hy\(hy\ \fIRemote operations\fR
.LP
summarize Summarize ::= 20
.LP
list List ::= 21
.LP
fetch Fetch ::= 22
.LP
delete Delete ::= 23
.LP
register\(hyms Register\(hyMS::= 24
.LP
alert Alert ::= 25
.LP
.sp 2
.LP
\(hy\(hy\ \fIRemote errors\fR
.LP
attribute\(hyerror AttributeError ::= 21
.LP
auto\(hyaction\(hyrequest\(hyerror AutoActionRequestError ::= 22
.LP
delete\(hyerror DeleteError ::= 23
.LP
fetch\(hyrestriction\(hyerror FetchRestrictionError ::= 24
.LP
range\(hyerror RangeError ::= 25
.LP
security\(hyerror SecurityError ::= 26
.LP
service\(hyerror ServiceError ::= 27
.ce 1000
FIGURE\ 4/X.419\ (Part 3 of 4)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MS access protocol (P7)\fR
.ce 0
.sp 1P
.LP
.sp 6
.LP
sequence\(hynumber\(hyerror SequenceNumberError ::= 28
.LP
.sp 2
END\ \(hy\(hy\ \fIof MSAccessProtocol\fR
.ce 1000
FIGURE\ 4/X.419\ (Part 4 of 4)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MS access protocol (P7)\fR
.ce 0
.sp 1P
.LP
.bp
.sp 2P
.LP
\fB9\fR \fBMapping onto used services\fR
.sp 1P
.RT
.PP
This paragraph defines the mapping of the MHS access protocols onto the
used services.
.PP
Paragraph 9.1 defines the mapping onto used services for
application\(hycontexts that omit the RTSE. Paragraph\ 9.2 defines the
mapping onto used services for application contexts that include the RTSE.
.RT
.sp 1P
.LP
9.1
\fIApplication\(hycontexts omitting RTSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MHS access protocols onto the
used services for application\(hycontexts that omit the RTSE. Support for
this mapping is optional for conformance to this Recommendation.
.RT
.sp 1P
.LP
9.1.1
\fIMapping onto ACSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the abstract\(hybind (MTS\(hybind
or MS\(hybind) and abstract\(hyunbind (MTS\(hyunbind or MS\(hyunbind) services
onto the
services of the ACSE in normal mode for application\(hycontexts that omit the
RTSE. The ACSE is defined in Recommendation\ X.217.
.RT
.sp 1P
.LP
9.1.1.1
\fIAbstract\(hybind onto A\(hyASSOCIATE\fR
.sp 9p
.RT
.PP
The abstract\(hybind service is mapped onto the A\(hyASSOCIATE service
of the ACSE. The use of the parameters of the A\(hyASSOCIATE service is
qualified in the following paragraphs.
.RT
.sp 1P
.LP
9.1.1.1.1
\fIMode\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association in the A\(hyASSOCIATE request primitive, and shall have the value
\*Qnormal mode\*U.
.RT
.sp 1P
.LP
9.1.1.1.2
\fIApplication context name\fR
.sp 9p
.RT
.PP
The initiator of the association shall propose one of the
application\(hycontexts defined in this Recommendation that omit the RTSE
in the A\(hyASSOCIATE request primitive (see Table\ 1/X.419).
.RT
.sp 1P
.LP
9.1.1.1.3
\fIUser information\fR
.sp 9p
.RT
.PP
The mapping of the bind\(hyoperation of the abstract\(hybind service onto
the user information parameter of the A\(hyASSOCIATE request primitive
is defined in Recommendation\ X.219.
.RT
.sp 1P
.LP
9.1.1.1.4
\fIPresentation context definition list\fR
.sp 9p
.RT
.PP
The initiator of the association shall supply the presentation
context definition list in the A\(hyASSOCIATE request primitive.
.PP
The presentation context definition list comprises a
presentation\(hycontext\(hydefinition for each abstract\(hysyntax included
in the
application\(hycontext. A presentation\(hycontext\(hydefinition comprises a
presentation\(hycontext\(hyidentifier and an abstract\(hysyntax\(hyname
for the ASE. Each named abstract syntax for the MSSE, MDSE, MRSE and MASE
includes the ROSE
APDUs.
.PP
Paragraphs 7 and 8 define the abstract\(hysyntaxes included in the
application\(hycontexts.
.RT
.sp 1P
.LP
9.1.1.1.5
\fIQuality of service\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association in the A\(hyASSOCIATE request primitive, and by the responder
of the association in the A\(hyASSOCIATE response primitive. The parameters
\*Qextended
control\*U and \*Qoptimized dialogue transfer\*U shall be set to not required.
The
remaining parameters shall be such that default values are used.
.RT
.sp 1P
.LP
9.1.1.1.6
\fISession requirements\fR
.sp 9p
.RT
.PP
This parameter shall be set by the initiator of the association in the
A\(hyASSOCIATE request primitive, and by the responder of the association
in the A\(hyASSOCIATE response primitive. The parameter shall be set to
specify the following functional units:
.RT
.LP
a)
kernel
.LP
b)
duplex.
.bp
.sp 1P
.LP
9.1.1.2
\fIAbstract\(hyunbind onto A\(hyRELEASE\fR
.sp 9p
.RT
.PP
The abstract\(hyunbind service is mapped onto the A\(hyRELEASE service
of the ACSE. The use of the parameters of the A\(hyRELEASE service is qualified
in
the following paragraphs.
.RT
.sp 1P
.LP
9.1.1.2.1
\fIResult\fR
.sp 9p
.RT
.PP
This parameter shall have the value \*Qaffirmative\*U.
.RT
.sp 1P
.LP
9.1.1.3
\fIUse of A\(hyABORT and A\(hyP\(hyABORT services\fR
.sp 9p
.RT
.PP
The ROSE is the user of the A\(hyABORT and A\(hyP\(hyABORT services\fR
of the ACSE.
.RT
.sp 1P
.LP
9.1.2
\fIMapping onto ROSE\fR
.sp 9p
.RT
.PP
The MSSE, MDSE, MRSE and MASE services are mapped onto the
RO\(hyINVOKE, RO\(hyRESULT, RO\(hyERROR, RO\(hyREJECT\(hyU and RO\(hyREJECT\(hyP
services of the
ROSE. The mapping of the abstract\(hysyntax notation of the MSSE, MDSE,
MRSE and MASE onto the ROSE services is as defined in Recommendation\ X.219.
.RT
.sp 1P
.LP
9.2
\fIApplication\(hycontexts including RTSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MHS access protocols onto the
used services for application\(hycontexts that include the RTSE in normal
mode. Support for this mapping is optional for conformance to this
Recommendation. No mappings are defined onto the RTSE in X.410\(hy1984\
mode. The RTSE is defined in Recommendation\ X.218.
.RT
.sp 1P
.LP
9.2.1
\fIMappint onto RT\(hyOPEN and RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the abstract\(hybind (MTS\(hybind
or MS\(hybind) and abstract\(hyunbind (MTS\(hyunbind or MS\(hyunbind) services
onto the
RT\(hyOPEN and RT\(hyCLOSE services of the RTSE in normal mode.
.RT
.sp 1P
.LP
9.2.1.1
\fIAbstract\(hybind onto RT\(hyOPEN\fR
.sp 9p
.RT
.PP
The abstract\(hybind service is mapped onto the RT\(hyOPEN service of the
RTSE. The use of the parameters of the RT\(hyOPEN service is qualified
in the
following paragraphs.
.RT
.sp 1P
.LP
9.2.1.1.1
\fIMode\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association in the RT\(hyOPEN request primitive, and shall have the value
\*Qnormal mode\*U.
.RT
.sp 1P
.LP
9.2.1.1.2
\fIApplication context name\fR
.sp 9p
.RT
.PP
The initiator of the association shall propose one of the
application\(hycontexts defined in this Recommendation that include the RTSE in
normal mode in the RT\(hyOPEN request primitive (see Table\ 1/X.419).
.RT
.sp 1P
.LP
9.2.1.1.3
\fIUser\(hydata\fR
.sp 9p
.RT
.PP
The mapping of the bind\(hyoperation of the abstract\(hybind service onto
the user\(hydata parameter of the RT\(hyOPEN request primitive is defined
in
Recommendation\ X.219.
.RT
.sp 1P
.LP
9.2.1.1.4
\fIPresentation context definition list\fR
.sp 9p
.RT
.PP
The initiator of the association shall supply the presentation
context definition list in the RT\(hyOPEN request primitive.
.PP
The presentation context definition list comprises a
presentation\(hycontext\(hydefinition for each abstract\(hysyntax included
in the
application context. A presentation\(hycontext\(hydefinition comprises a
presentation\(hycontext\(hyidentifier and an abstract\(hysyntax\(hyname
for the ASE. Each named abstract\(hysyntax for the MSSE, MDSE, MRSE and
MASE includes the ROSE
APDUs. The named abstract\(hysyntax for the RTSE includes the abstract\(hysyntax
for the bind\(hyoperation of the abstract\(hybind service.
.PP
Paragraphs 7 and 8 define the abstract\(hysyntaxes included in the
application\(hycontexts.
.RT
.sp 1P
.LP
9.2.1.2
\fIAbstract\(hyunbind onto RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
The abstract\(hyunbind service is mapped onto the RT\(hyCLOSE service of
the RTSE.
.bp
.RT
.sp 1P
.LP
9.2.2
\fIMapping onto ROSE\fR
.sp 9p
.RT
.PP
The MSSE, MDSE and MASE services are mapped onto the RO\(hyINVOKE,
RO\(hyRESULT, RO\(hyERROR, RO\(hyREJECT\(hyU and RO\(hyREJECT\(hyP services
of the ROSE. The
mapping of the abstract\(hysyntax notation of the MSSE, MDSE, MRSE and
MASE onto the ROSE services is performed as defined in Recommendation\
X.219.
.PP
ROSE is the user of the RT\(hyTRANSFER, RT\(hyTURN\(hyPLEASE, RT\(hyTURN\(hyGIVE,
RT\(hyP\(hyABORT and RT\(hyU\(hyABORT services of the RTSE. The use of
the RTSE services by the ROSE is defined in Recommendation\ X.229.
.RT
.sp 1P
.LP
9.2.2.1
\fIManaging the turn\fR
.sp 9p
.RT
.PP
Recommendation X.229 defines the use by the ROSE of the
RT\(hyTURN\(hyPLEASE and RT\(hyTURN\(hyGIVE services of the RTSE to manage
the turn.
.PP
Table 2/X.419 defines the values of the priority parameter of the
RT\(hyTURN\(hyPLEASE service used by the ROSE to request the turn.
.PP
Priority zero is the highest priority, and is reserved for the action of
releasing the association by the initiator.
.PP
Priority one is used by the ROSE for the RORJ APDU and ROER APDU to
provide the RO\(hyREJECT\(hyU and RO\(hyERROR services of the ROSE.
.PP
Priority two is used by the ROSE for the RORS APDU to provide the
RO\(hyRESULT services of the ROSE.
.PP
Priority three to seven shall be used for the ROIV APDU to provide the
RO\(hyINVOKE service for the MHS access protocol remote operations. In
the case of a remote operation whose arguments include a message, the ROIV
APDU is
prioritized as a function of the \fBpriority\fR of the message \(em\ \fBurgent,
normal\fR or \fBnon\(hyurgent\fR .
.RT
.ce
\fBH.T. [T2.419]\fR
.ce
TABLE\ 2/X.419
.ce
\fBRemote operation priorities\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(24p) | cw(54p) | cw(48p) | cw(54p) | cw(48p) .
Priority MSSE MDSE MRSE MASE
_
.T&
cw(24p) | lw(204p) .
0 Association release
_
.T&
cw(24p) | lw(204p) .
1 T{
RO\(hyREJECT\(hyU
RO\(hyERROR
T}
_
.T&
cw(24p) | lw(204p) .
2 RO\(hyRESULT
_
.T&
cw(24p) | lw(54p) | lw(48p) | lw(54p) | lw(48p) .
3 Submission\(hycontrol Delivery\(hycontrol
_
.T&
cw(24p) | lw(54p) | lw(48p) | lw(54p) | lw(48p) .
4 T{
Message\(hysubmission
(urgent)
T} Message\(hydelivery (urgent) Alert
_
.T&
cw(24p) | lw(54p) | lw(48p) | lw(54p) | lw(48p) .
5 Probe\(hysubmission Report\(hydelivery T{
Register\(hyMS
Summarize
List\fR
Fetch
Delete
T} T{
Register
Change\(hycredentials
T}
_
.T&
cw(24p) | lw(54p) | lw(48p) | lw(54p) | lw(48p) .
6 T{
Message\(hysubmission
(normal)
T} T{
Message\(hydelivery
(normal)
T}
_
.T&
cw(24p) | lw(54p) | lw(48p) | lw(54p) | lw(48p) .
7 T{
Message\(hysubmission
(non\(hyurgent)
T} Message\(hydelivery
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 2/X.419 [T2.419], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fB10\fR \fBConformance\fR
.sp 1P
.RT
.PP
A system (UA, MS or MTA) claiming conformance to the MHS access
protocols specified in this Recommendation shall comply with the requirements
in \(sc\(sc\ 10.1, 10.2 and 10.3.
.RT
.sp 1P
.LP
10.1
\fIStatement requirements\fR
.sp 9p
.RT
.PP
The following shall be stated:
.RT
.LP
a)
the type of system for which conformance is claimed (UA, MS, MTA or MTA/MS);
.LP
b)
the application\(hycontexts defined in Section\ 2 of this
Recommendation for which conformance is claimed.
.PP
Conformance can be claimed to the MTS access protocol (P3), or the MS access
protocol (P7), or both. Table\ 3/X.419 classifies the support for
application\(hycontexts required for conformance to the MTS access protocol
(P3). Table\ 4/X.419 classifies the support for application\(hycontexts
required for
conformance to the MS access protocol (P7).
.ce
\fBH.T. [T3.419]\fR
.ce
TABLE\ 3/X.419
.ce
\fBMTS access protocol conformance requirements\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(72p) | cw(60p) | cw(60p) .
Application context MTA \fR MTS\(hyuser
_
.T&
lw(72p) | lw(60p) | lw(60p) .
\fIMTS access protocol\fR
.T&
lw(72p) | lw(60p) | lw(60p) .
mts\(hyaccess Mandatory Optional
.T&
lw(72p) | lw(60p) | lw(60p) .
mts\(hyforced\(hyaccess Mandatory Optional
.T&
lw(72p) | lw(60p) | lw(60p) .
mts\(hyreliable\(hyaccess Optional (see note) Optional
.T&
lw(72p) | lw(60p) | lw(60p) .
T{
mts\(hyforced\(hyreliable\(hyaccess
T} Optional (see note) T{
Optional
\fINote\fR
\ \(em\ If an MTA claims conformance to the mts\(hyreliable\(hyaccess
application\(hycontext, it shall also claim conformance to the
mts\(hyforced\(hyreliable\(hyaccess application\(hycontext, and vice versa.
.parag
T}
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 3/X.419 [T3.419], p.\fR
.sp 1P
.RT
.ad b
.RT
.ce
\fBH.T. [T4.419]\fR
.ce
TABLE\ 4/X.419
.ce
\fBMS access protocol conformance requirements \fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(60p) | cw(48p) | cw(48p) .
Application context MS MS\(hyuser
_
.T&
lw(60p) | lw(48p) | lw(48p) .
\fIMS access protocol\fR
.T&
lw(60p) | lw(48p) | lw(48p) .
ms\(hyaccess Mandatory Optional
.T&
lw(60p) | lw(48p) | lw(48p) .
ms\(hyreliable\(hyaccess Optional Optional
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 4/X.419 [T4.419], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
10.2
\fIStatic requirements\fR
.sp 9p
.RT
.PP
The system shall:
.RT
.LP
a)
conform to the abstract\(hysyntax definition(s) of the MHS
access protocols defined in \(sc\(sc\ 7 and\ 8 of this Recommendation,
required by the application\(hycontexts for which conformance is claimed.
.bp
.sp 1P
.LP
10.3
\fIDynamic requirements\fR
.sp 9p
.RT
.PP
The system shall:
.RT
.LP
a)
conform to the mapping onto used services defined in \(sc 9 of this Recommendation,
required by the application\(hycontexts for which conformance is claimed;
.LP
b)
conform to the use of underlying services defined in \(sc 6.4 of this
Recommendation.
.LP
SECTION\ 3\ \(em
MESSAGE\ TRANSFER\ SYSTEM\ TRANSFER\ PROTOCOL\ SPECIFICATION
.sp 1P
.RT
.sp 2P
.LP
\fB11\fR \fBOverview of the MTS transfer protocol\fR
.sp 1P
.RT
.sp 1P
.LP
11.1
\fIModel\fR
.sp 9p
.RT
.PP
Paragraph 10 of Recommendation\ X.411 refines the abstract model of the
message transfer system (MTS), first presented in \(sc\ 6 of that
Recommendation, to reveal that the MTS object comprises a collection of
message\(hytransfer\(hyagent (MTA) objects, which cooperate together to
form the MTS and offer the MTS abstract service to its users.
.PP
In the refined abstract model, interactions between MTAs are modelled as
a set of abstract operations which occur at the transfer\(hyport paired
between MTAs.
.PP
This paragraph describes how the MTA abstract service is supported by instances
of OSI communication when the MTAs are realised as
application\(hyprocesses located in different open systems.
.PP
In the OSI environment, communication between application\(hyprocesses
is represented in terms of communication between a pair of application\(hyentities
(AEs) using the presentation\(hyservice. The functionality of an AE is factored
into a set of one or more application\(hyservice\(hyelements (ASEs). The
interaction between AEs is described in terms of their use of the services
provided by the ASEs.
.PP
The transfer\(hyport services of the abstract model are supported by an
application\(hyservice\(hyelement\ \(em the message transfer service element
(MTSE),
which in turn is supported by two other application\(hyservice\(hyelements\
\(em the
reliable transfer service element (RTSE) and the association control service
element (ACSE).
.PP
The reliable transfer service element (RTSE) is used to reliably
transfer application\(hyprotocol\(hydata\(hyunits (APDUs) that contain
the message,
probes and reports between AEs.
.PP
The association control service element (ACSE) supports the
establishment and release of an application\(hyassociation between a pair
of AEs. Associations between MTAs can be established by either MTA. Only
the initiator of an established association can release it.
.PP
The combination of the MTSE, the RTSE and the ACSE defines the
application\(hycontext of an application\(hyassociation.
.PP
Figure 4/X.419 models the application\(hycontext between MTAs.
.PP
Three application\(hycontexts are defined for the MTS transfer protocol
as identified in Table\ 5/X.419.
.RT
.ce
\fBH.T. [T5.419]\fR
.ce
TABLE\ 5/X.419
.ce
\fBMTS transfer protocol application contexts\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Application context P1 RTSE mode
_
.T&
lw(90p) | lw(30p) | lw(36p) .
T{
mts\(hytransfer\(hyprotocol\(hy1984
T} P1 1984 X.410\(hy1984
_
.T&
lw(90p) | lw(30p) | lw(36p) .
mts\(hytransfer\(hyprotocol P1 1988 X.410\(hy1984
_
.T&
lw(90p) | lw(30p) | lw(36p) .
mts\(hytransfer P1 1988 normal
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 5/X.419 [T5.419], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.PP
The \fBmts\(hytransfer\(hyprotocol\(hy1984\fR is defined for interworking
with implementations of the 1984 Recommendation\ X.411. In this application\(hycontext,
the abstract\(hysyntax of the MTSE is constrained to that defined in the
1984
Recommendation\ X.411. These constraints are identified by
underlining
of the 1988 extensions to the abstract syntax of the MTSE in the defining
ASN.1 module in Recommendation\ X.411. The changes are also listed in Annex\
C of this Recommendation for reference. The \fBmts\(hytransfer\(hyprotocol\(hy1984\fR
is supported by the RTSE in X.410\(hy1984 mode. Support for the \fBmts\(hytransfer\(hyprotocol\(hy1984\fR
is mandatory for conformance to this Recommendation.
.PP
The \fBmts\(hytransfer\(hyprotocol\fR is defined to enable interworking
between implementations which support the 1988 extended functionality via
systems which have had a minimal upgrade from conformance to the 1984 Recommendation\
X.411. The \fBmts\(hytransfer\(hyprotocol\fR provides for controlled transparency
of the
upgraded system to the 1988 extensions. The \fBmts\(hytransfer\(hyprotocol\fR
is
supported by the RTSE in X.410\(hy1984 mode. Support for the
\fBmts\(hytransfer\(hyprotocol\fR is mandatory for conformance to this
Recommendation.
.PP
The \fBmts\(hytransfer\fR application\(hycontext is supported by the RTSE in
normal mode. It is envisaged that, over time, most systems will migrate to
support the \fBmts\(hytransfer\fR application\(hycontext. Support for the
\fBmts\(hytransfer\fR application\(hycontext is optional for conformance
to this Recommendation. Note
that in ISO\ 10021\(hy6 support for the \fBmts\(hytransfer\fR application\(hycontext
is
mandatory. A future version of this Recommendation is likely to make support
for the \fBmts\(hytransfer\fR application\(hycontext mandatory as part
of a migration
strategy to enable support for extended functionaility and to maximise
interworking.
.RT
.LP
.rs
.sp 22P
.ad r
\fBFigure 4/X.419, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
11.2
\fIServices provided by the MTS transfer protocol\fR
.sp 9p
.RT
.PP
The MTS transfer protocol (P1) provides the following services
defined in Recommendation\ X.411:
.RT
.LP
\fIMTA\(hybind and MTA\(hyunbind\fR
.LP
a)
MTA\(hybind
.LP
b)
MTA\(hyunbind
.LP
\fIMessage transfer service element (MTSE)\fR
.LP
c)
message\(hytransfer
.LP
d)
probe\(hytransfer
.LP
e)
report\(hytransfer
.bp
.sp 1P
.LP
11.3
\fIUse of underlying services\fR
.sp 9p
.RT
.PP
The MTS transfer protocol (P1) makes use of underlying services as described
below.
.RT
.sp 1P
.LP
11.3.1
\fIUse of the RTSE services\fR
.sp 9p
.RT
.PP
The reliable transfer service element (RTSE) is defined in
Recommendation\ X.218.
.PP
The RTSE provides for the reliable transfer of
application\(hyprotocol\(hydata\(hyunits (APDUs). The RTSE ensures that
each APDU is
completely transferred once, or that the sender is warned of an exception.
The RTSE recovers from communication and end\(hysystem failure and minimises
the
amount of retransmission needed for recovery.
.PP
The RTSE services are used to support the MTS transfer protocol (P1). Support
for RTSE in X.410\(hy1984 mode is mandatory. Support for the RTSE in
normal mode is optional. Note that in ISO\ 10021\(hy6, support for the RTSE in
normal mode is mandatory, and support for the RTSE in X.410\(hy1984 is
optional.
.PP
The use of the X.410\(hy1984 mode of the RTSE implies the use of the
X.410\(hy1984 mode of the ACSE and the X.410\(hy1984 mode of the
presentation\(hyservice. The use of the normal mode of the RTSE implies
the use of the normal mode of the ACSE and the normal mode of the presentation\(hyservice.
.PP
The MTS transfer protocol (P1) is the sole user of the RT\(hyOPEN,
RT\(hyCLOSE, RT\(hyTRANSFER, RT\(hyTURN\(hyPLEASE, RT\(hyTURN\(hyGIVE,
RT\(hyP\(hyABORT and RT\(hyU\(hyABORT services of the RTSE.
.RT
.sp 1P
.LP
11.3.2
\fIUse of the ACSE services\fR
.sp 9p
.RT
.PP
The association control service element (ACSE) is defined in
Recommendation\ X.217.
.PP
The ACSE provides for the control (establishment, release, abort) of application\(hyassociations
between AEs.
.PP
The RTSE is the sole user of the A\(hyASSOCIATE, A\(hyRELEASE, A\(hyABORT
and A\(hyP\(hyABORT services of the ACSE. The use of the X.410\(hy1984
mode of the RTSE
implies the use of the X.410\(hy1984 mode of the ACSE and the X.410\(hy1984
mode of the presentation\(hyservice. The use of the normal mode of the
RTSE implies the
use of the normal mode of the ACSE and the normal mode of the
presentation\(hyservice.
.RT
.sp 1P
.LP
11.3.3
\fIUse of the presentation\(hyservice\fR
.sp 9p
.RT
.PP
The presentation\(hyservice is defined in Recommendation\ X.216.
.PP
The presentation layer coordinates the representation (syntax) of the application
layer semantics that are to be exchanged.
.PP
In X.410\(hy1984 mode, a single default presentation\(hycontext is used
for the underlying presentation\(hyconnection. This presentation\(hycontext
includes a
single abstract\(hysyntax for all of the ASEs included in the application\(hycontext
(i.e.\ MTSE, RTSE and ACSE).
.PP
In normal mode, a different presentation\(hycontext is used for each
abstract\(hysyntax included in the application\(hycontext.
.PP
Presentation layer addressing is not used for the message transfer
protocol (P1) in X.410\(hy1984 mode.
.PP
The ACSE is the sole user of the P\(hyCONNECT, P\(hyRELEASE, P\(hyU\(hyABORT
and P\(hyP\(hyABORT services of the presentation\(hyservice.
.PP
The RTSE is the sole user of the P\(hyACTIVITY\(hySTART, P\(hyDATA,
P\(hyMINOR\(hySYNCHRONIZE,
P\(hyACTIVITY\(hyEND, P\(hyACTIVITY\(hyINTERRUPT, P\(hyACTIVITY\(hyDISCARD,
P\(hyU\(hyEXCEPTION\(hyREPORT,
P\(hyACTIVITY\(hyRESUME, P\(hyP\(hyEXCEPTION\(hyREPORT, P\(hyTOKEN\(hyPLEASE,
and P\(hyCONTROL\(hyGIVE services of the presentation service. The use
of the
X.410\(hy1984 mode of the RTSE implies the use of the X.410\(hy1984 mode
of the\ ACSE and the X.410\(hy1984 mode of the presentation\(hyservice.
The use of the normal mode of the RTSE implies the use of the normal mode
of the ACSE and the normal mode of the presentation\(hyservice.
.bp
.RT
.sp 1P
.LP
11.3.4
\fIUse of lower layer services\fR
.sp 9p
.RT
.PP
The session\(hyservice is defined in Recommendation\ X.215. The session
layer structures the dialogue of the flow of information between the
end\(hysystems.
.PP
The use of the RTSE requires the use of the kernel, half\(hyduplex,
exceptions, minor\(hysynchronize and activity\(hymanagement functional
units by the presentation layer.
.PP
Session layer addressing is not used for the MTS transfer protocol
(P1) when the RTSE is used in X.410\(hy1984 mode. That is, a session\(hyaddress
shall not be passed in the Connect SPDU of the session layer.
.PP
The transport\(hyservice is defined in Recommendation\ X.214. The
transport layer provides for the end\(hyto\(hyend transparent transfer
of data over the underlying network connection.
.PP
The choice of the class of transport\(hyservice used by the session layer
depends on the requirements for multiplexing and error recovery. Support
for
Class\ 0 is mandatory. Transport expedited services is not used.
.PP
Support for other classes is optional. The use of an error recovery
class together with the RTSE duplicates mechanisms for error recovery.
.PP
The transport\(hyaddress comprises a network\(hyaddress and a
transport\(hyservice\(hyaccess\(hypoint identifier (TSAP\(hyidentifier). The
TSAO\(hyidentifier is carried in the transport layer protocol. When the RTSE is
used in X.410\(hy1984\ mode, it consists of up to sixteen IA5\ digits.
.PP
An underlying network supporting the OSI network\(hyservice defined in
Recommendation\ X.213 is assumed.
.PP
A network\(hyaddress is as defined in Recommendation X.121,
Recommendations\ E.163/E.164, or Recommendation\ X.200 (OSI NSAP\(hyaddress).
.RT
.sp 1P
.LP
11.4
\fIEstablishing and releasing associations\fR
.sp 9p
.RT
.PP
Associations between two MTAs are created in accordance with
bilateral agreements covering the following:
.RT
.LP
a)
the maximum number of associations that may exist
simultaneously;
.LP
b)
whether monologue or two\(hyway\(hyalternate associations are
used;
.LP
c)
which application\(hycontext is used;
.LP
d)
which MTA has responsibility for establishing the
associations;
.LP
e)
whether associations are permanently established or
established and released as required.
.sp 2P
.LP
\fB12\fR \fBMTS transfer protocol abstract syntax definition\fR
.sp 1P
.RT
.PP
The abstract\(hysyntax of the MTS transfer protocol (P1) is defined in
Figure\ 5/X.419.
.PP
The abstract\(hysyntax of the MTS transfer protocol (P1) is defined using
the abstract\(hysyntax notation (ASN.1) defined in Recommendation\ X.208,
and the remote operations notation defined in Recommendation\ X.219.
.PP
The abstract\(hysyntax definition of the MTS transfer protocol (P1) has
the following major parts:
.RT
.LP
\(em
\fIPrologue:\fR \| declarations of the exports from, and imports
to, the MTS transfer protocol (P1) module (Figure\ 5/X.419, Part\ 1).
.LP
\(em
\fIApplication contexts:\fR \| definitions of the
application\(hycontexts used between MTAs (Figure\ 5/X.419, Part\ 2).
.LP
\(em
\fIMessage transfer service element:\fR \| definitions of the
message transfer service element (MTSE) (Figure\ 5/X.419, Part\ 3).
.LP
\(em
\fIMTS application protocol data units:\fR \| definition of the MTS application\(hyprotocol\(hydata\(hyunits
(APDUs): message, probe and report
(Figure\ 5/X.419, Part\ 3).
.LP
.rs
.sp 2P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
MTSTransferProtocol\|{\|joint\(hyiso\(hyccitt mhs\(hymotis(6) protocols(0)
modules(0) transfer\(hyprotocol(3)\|}
.LP
DEFINITIONS IMPLICIT TAGS ::=
.LP
BEGIN
.LP
.sp 2
\(hy\(hy\ \fIPrologue\fR
.LP
EXPORTS;
.LP
IMPORTS
.LP
\(hy\(hy\ \fIApplication service elements and application contexts\fR
.LP
APPLICATION\(hySERVICE\(hyELEMENT, APPLICATION\(hyCONTEXT, aCSE
.LP
FROM Remote\(hyOperations\(hyNotation\(hyextension\|{\|joint\(hyiso\(hyccitt
remote\(hyoperations(4)
.LP
\ \ notation\(hyextension(2)\|}
.LP
rTSE
.LP
FROM Reliable\(hyTransfer\(hyAPDUs\|{\|joint\(hyiso\(hyccitt reliable\(hytransfer(3)
apdus(0)\|}
.LP
\(hy\(hy\ \fIMTA transfer port abstract service parameters\fR
.LP
MTABind, MTAUnbind, Message, Probe, Report,
.LP
FROM MTAAbstractService {\|joint\(hyiso\(hyccitt mhs\(hymotis(6) mts(3)
modules (0)
.LP
\ \ mta\(hyabstract\(hyservice(2)\|}
.LP
\(hy\(hy\ \fIObject identifiers\fR
.LP
id\(hyac\(hymts\(hytransfer, id\(hyas\(hyacse, id\(hyas\(hymta\(hyrtse,
id\(hyas\(hymtse, id\(hyase\(hymtse
.LP
FROM MHSProtocolObjectIdentifiers {\|joint\(hyiso\(hyccitt mhs\(hymotis(6)
protocols(0)
.LP
\ \ modules(0) object\(hyidentifiers(0)\|}
.ce 1000
FIGURE\ 5/X.419\ (Part 1 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS transfer protocol (P1)\fR
.ce 0
.sp 1P
.LP
.sp 6
.LP
\(hy\(hy\ \fIApplication context including RTSE in normal mode\fR
.LP
mts\(hytransfer APPLICATION\(hyCONTEXT
.LP
APPLICATION SERVICE ELEMENTS {\|aCSE, rTSE, mTSE\|}
.LP
BIND MTABind
.LP
UNBIND MTAUnbind
.LP
ABSTRACT SYNTAXES\|{
.LP
id\(hyas\(hyacse,
\(hy\(hy\ of ACSE
.LP
id\(hyas\(hymts\(hyrtse,
\(hy\(hy\ of MTABind and MTAUnbind, including RTSE
.LP
id\(hyas\(hymtse
\(hy\(hy\ of MTSE\(hy\(hy\|}
.LP
::= id\(hyac\(hymts\(hytransfer
.LP
.sp 2
\(hy\(hy\ \fIApplication context including RTSE in X.410\(hy1984 mode\fR
.LP
mts\(hytransfer\(hyprotocol INTEGER ::= 12
.LP
.sp 2
\(hy\(hy\ \fIApplication context for interworking with 1984 P1\fR
.LP
mts\(hytransfer\(hyprotocol\(hy1984 INTEGER ::= 1
.ce 1000
FIGURE\ 5/X.419\ (Part 2 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS transfer protocol (P1)\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIMessage transfer service element\fR
.LP
mTSE APPLICATION\(hySERVICE\(hyELEMENT
.LP
::= id\(hyase\(hymtse
.LP
.sp 2
\(hy\(hy\ \fIMTS application protocol data units\fR
.LP
MTS\(hyAPDU ::= CHOICE\|{
.LP
message [0] Message,
.LP
probe [2] Probe,
.LP
report [1] Report\|}
.LP
.sp 2
END\ \(hy\(hy\ \fIof MTSTransferProtocol\fR
.ce 1000
FIGURE\ 5/X.419\ (Part 3 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of the MTS transfer protocol (P1)\fR
.ce 0
.sp 1P
.LP
.sp 6
.sp 2P
.LP
\fB13\fR \fBMapping onto used services\fR
.sp 1P
.RT
.PP
This paragraph defines the mapping of the MTS transfer protocol
(P1) onto the used services.
.PP
Paragraph 13.1 defines the mapping of the MTS transfer protocol (P1) onto
used services for application\(hycontexts that include the RTSE in X.410\(hy1984
mode. Paragraph\ 13.2 defines the mapping of the MTS transfer protocol
(P1)
onto used services for application\(hycontexts that include the RTSE in normal
mode.
.RT
.sp 1P
.LP
13.1
\fIMapping onto RTSE X.410\(hy1984 mode\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MTS transfer protocol
(P1) onto used services for application\(hycontexts that include the RTSE in
X.410\(hy1984 mode. Support for this mapping is mandatory for conformance
to this Recommendation.
.PP
Paragraph 13.1.1 defines the mapping of the MTA\(hybind and MTA\(hyunbind
services onto the RT\(hyOPEN and RT\(hyCLOSE services of the RTSE in X.410\(hy1984
mode. Paragraph\ 13.1.2 defines the mapping of the message\(hytransfer,
probe\(hytransfer
and report\(hytransfer services onto the RT\(hyTRANSFER service of the RTSE.
Paragraph\ 13.1.3 describes managing the turn using the RT\(hyTURN\(hyPLEASE
and
RT\(hyTURN\(hyGIVE services of the RTSE. Paragraph\ 13.1.4 defines the
use of the
RT\(hyP\(hyABORT service of the RTSE. Paragraph\ 13.1.5 defines the use of the
RT\(hyU\(hyABORT service of the RTSE (not used in X.410\(hy1984 mode).
.RT
.sp 1P
.LP
13.1.1
\fIMapping onto RT\(hyOPEN and RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MTA\(hybind and MTA\(hyunbind
services onto the RT\(hyOPEN and RT\(hyCLOSE services of the RTSE in X.410\(hy1984
mode.
.RT
.sp 1P
.LP
13.1.1.1\ \ \fIMTA\(hybind onto RT\(hyOPEN\fR
.sp 9p
.RT
.PP
The MTA\(hybind service is mapped onto the RT\(hyOPEN service of the
RTSE. The use of the parameters of the RT\(hyOPEN service is qualified in the
following clauses.
.RT
.sp 1P
.LP
13.1.1.1.1\ \ \fIApplication\(hyprotocol\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association of the RT\(hyOPEN request primitive, and shall have the value
\fBmts\(hytransfer\(hyprotocol\fR (an integer value of \*Q12\*U) or
\fBmts\(hytransfer\(hyprotocol\(hy1984\fR (an integer value of \*Q1\*U).
.bp
.RT
.sp 1P
.LP
13.1.1.1.2\ \ \fIUser\(hydata\fR
.sp 9p
.RT
.PP
The value of the type defined in the ARGUMENT clause of the
MTA\(hybind service is mapped onto the user\(hydata parameter of the RT\(hyOPEN
request primitive by the initiator of the association.
.PP
If the responder of the association supplies the result parameter of the
RT\(hyOPEN response primitive with the value \*Qaccepted\*U, the value
of the type defined in the RESULT clause of the MTA\(hybind service is
mapped onto the
user\(hydata parameter of the RT\(hyOPEN response primitive.
.PP
In the case of error the responder of the association supplies the
result parameter of the RT\(hyOPEN response primitive with the \*Qrejected
(permanent)\*U or \*Qrejected (transient)\*U. In the case of \*Qrejected
(permanent)\*U, the user\(hydata parameter of the RT\(hyOPEN response primitive
shall be either
authentication\(hyerror or unacceptable\(hydialogue\(hymode.
.RT
.sp 1P
.LP
13.1.1.1.3\ \ \fIMode\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association in the RT\(hyOPEN request primitive, and shall have the value
\*QX.410\(hy1984 mode\*U.
.RT
.sp 1P
.LP
13.1.1.2\ \ \fIMTA\(hyunbind onto RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
The MTA\(hyunbind is mapped onto the RT\(hyCLOSE service of the RTSE. In
the X.410\(hy1984 mode, the RT\(hyCLOSE service has no parameters.
.RT
.sp 1P
.LP
13.1.2
\fIMapping onto RT\(hyTRANSFER\fR
.sp 9p
.RT
.PP
The message\(hytransfer, probe\(hytransfer and report\(hytransfer services
are mapped onto the RT\(hyTRANSFER service of the RTSE.
.PP
An MTSE may issue an RT\(hyTRANSFER request primitive only if it
possesses the turn (see \(sc\ 13.1.3) and if there is no outstanding RT\(hyTRANSFER
confirm primitive.
.PP
The use of the parameters of the RT\(hyTRANSFER service is qualified in
the following paragraphs.
.RT
.sp 1P
.LP
13.1.2.1\ \ \fIAPDU\fR
.sp 9p
.RT
.PP
The value of the MTS\(hyAPDU shall be mapped onto the APDU parameter of
the RT\(hyTRANSFER request primitive by the sender.
.PP
For the message\(hytransfer service, the MTS\(hyAPDU is a message. For
the probe\(hytransfer service, the MTS\(hyAPDU is a probe. For the report\(hytransfer
service, the MTS\(hyAPDU is a report.
.RT
.sp 1P
.LP
13.1.2.2\ \ \fITransfer\(hytime\fR
.sp 9p
.RT
.PP
The value of this parameter is specified by a local rule of the
sender. It may be related to the priority of the APDU (see \(sc\ 13.1.3.1.1).
.RT
.sp 1P
.LP
13.1.3
\fIManaging the turn\fR
.sp 9p
.RT
.PP
This paragraph describes managing the turn using the
RT\(hyTURN\(hyPLEASE and RT\(hyTURN\(hyGIVE services of the RTSE.
.PP
The MTSE must possess the turn before it can use the RT\(hyTRANSFER
service to transfer a message, probe or report.
.PP
The MTSE without the turn may issue an RT\(hyTURN\(hyPLEASE request
primitive, the priority parameter of which reflects the highest priority
APDU awaiting transfer.
.PP
The MTSE with the turn may issue an RT\(hyTURN\(hyGIVE request primitive
when it has no further APDUs to transfer. It shall issue an RT\(hyTURN\(hyGIVE
request primitive in response to an RT\(hyTURN\(hyPLEASE indication primitive
when it has no further APDUs to transfer of priority equal to, or higher
than, that
indicated in the RT\(hyTURN\(hyPLEASE indication primitive. If it has APDUs
of lower priority still to transfer, it may then issue an RT\(hyTURN\(hyPLEASE
request
primitive, the priority parameter of which reflects the highest priority
APDU awaiting transfer.
.bp
.RT
.sp 1P
.LP
13.1.3.1\ \ \fIUse of the\fR
\fIRT\(hyTURN\(hyPLEASE service\fR
.sp 9p
.RT
.PP
An MTSE issues the RT\(hyTURN\(hyPLEASE request primitive to request the
turn. It may do so only if it does not already possess the turn.
.PP
If the initiator of the association supplied a dialogue\(hymode parameter
value of \*Qmonologue\*U and an initial\(hyturn parameter value of
\*Qassociation\(hyinitiator\*U, the RT\(hyTURN\(hyPLEASE service shall
not be used.
.PP
The use of the parameter of the RT\(hyTURN\(hyPLEASE service is qualified
in the following paragraph.
.RT
.sp 1P
.LP
13.1.3.1.1\ \ \fIPriority\fR
.sp 9p
.RT
.PP
The value of the priority parameter is supplied by the MTSE
requesting the turn, and reflects the highest priority APDU awaiting transfer.
.PP
Priority zero is the highest priority, and is reserved for the action of
releasing the asociation by the initiator.
.PP
Priority one shall be assigned to messages whose priority field
(defined in \(sc\ 8.2.1.1.1.8 of Recommendation\ X.411) has the value urgent.
Priority one shall also be assigned to probes and reports.
.PP
Priority two shall be assigned to messages whose \fBpriority\fR field is
\fBnormal\fR .
.PP
Priority three shall be assigned to messages whose \fBpriority\fR field
is \fBnon\(hyurgent\fR .
.PP
If more than one association is established between two MTAs,
MTS\(hyAPDUs may be assigned to associations in accordance with their priorities.
Several associations may be used to carry MTS\(hyAPDUs of the same priority.
On
any one association, higher priority MTS\(hyAPDUs are sent before lower
priority MTS\(hyAPDUs; MTS\(hyAPDUs of the same priority are sent \*Qfirst\(hyin\(hyfirst\(hyout\*U.
.RT
.sp 1P
.LP
13.1.3.2\ \ \fIUse of the\fR
\fIRT\(hyTURN\(hyGIVE service\fR
.sp 9p
.RT
.PP
An MTSE issues the RT\(hyTURN\(hyGIVE request primitive to relinquish the
turn to its peer. It may do so only if it possesses the turn.
.PP
If the initiator of the association supplied a Dialogue\(hymode parameter
value of \*Qmonologue\*U and an Initial\(hyturn parameter value of
\*Qassociation\(hyinitiator\*U, the RT\(hyTURN\(hyGIVE service shall not
be used.
.PP
The RT\(hyTURN\(hyGIVE service has no parameters.
.RT
.sp 1P
.LP
13.1.4
\fIUse of the\fR
\fIRT\(hyP\(hyABORT service\fR
.sp 9p
.RT
.PP
The application\(hyprocess is the user of the RT\(hyP\(hyABORT service of
the RTSE.
.PP
The RT\(hyP\(hyABORT service provides an indication to the
application\(hyprocess that the application\(hyassociation cannot be maintained
(e.g.,\ because recovery not possible).
.PP
The RT\(hyP\(hyABORT service has no parameters.
.RT
.sp 1P
.LP
13.1.5
\fIUse of the\fR
\fIRT\(hyU\(hyABORT service\fR
.sp 9p
.RT
.PP
The RT\(hyU\(hyABORT service of the RTSE is not available in X.410\(hy1984
mode.
.RT
.sp 1P
.LP
13.2
\fIMapping onto\fR
\fIRTSE normal mode\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MTS transfer protocol
(P1) onto used services for application\(hycontexts that include the RTSE in
normal mode. Support for this mapping is optional for conformance to this
Recommendation. Note that ISO\ 10021\(hy6, support for the RTSE in normal
mode is mandatory.
.PP
Paragraph 13.2.1 defines the mapping of the MTA\(hybind and MTA\(hyunbind
services onto the RT\(hyOPEN and RT\(hyCLOSE services of the RTSE in normal
mode.
Paragraph\ 13.2.2 defines the mapping of the message\(hytransfer, probe\(hytransfer
and report\(hytransfer services onto the RT\(hyTRANSFER service of the RTSE.
Paragraph\ 13.2.3 describes managing the turn using the RT\(hyTURN\(hyPLEASE
and
RT\(hyTURN\(hyGIVE services of the RTSE. Paragraph\ 13.2.4 defines the
use of the
RT\(hyP\(hyABORT service of the RTSE. Paragraph\ 13.2.5 defines the use of the
RT\(hyU\(hyABORT service of the RTSE.
.bp
.RT
.sp 1P
.LP
13.2.1
\fIMapping onto RT\(hyOPEN and RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
This paragraph defines the mapping of the MTA\(hybine and MTA\(hyunbind
services onto the RT\(hyOPEN and RT\(hyCLOSE services of the RTSE in normal
mode.
.RT
.sp 1P
.LP
13.2.1.1\ \ \fIMTA\(hybind onto RT\(hyOPEN\fR
.sp 9p
.RT
.PP
The MTA\(hybind service is mapped onto the RT\(hyOPEN service of the
RTSE. The use of the parameters of the RT\(hyOPEN service is qualified in the
following paragraphs.
.RT
.sp 1P
.LP
13.2.1.1.1\ \ \fIMode\fR
.sp 9p
.RT
.PP
This parameter shall be supplied by the initiator of the
association in the RT\(hyOPEN request primitive, and shall have the value
\*Qnormal mode\*U.
.RT
.sp 1P
.LP
13.2.1.1.2\ \ \fIApplication context name\fR
.sp 9p
.RT
.PP
The initiator of the association shall propose the \fBmts\(hytransfer\fR
application\(hycontext defined in this Recommendation in the RT\(hyOPEN
request
primitive.
.RT
.sp 1P
.LP
13.2.1.1.3\ \ \fIUser\(hydata\fR
.sp 9p
.RT
.PP
The mapping of the bind\(hyoperation of the MTA\(hybind service onto the
user\(hydata parameter of the RT\(hyOPEN request primitive is defined in
Recommendation\ X.219.
.RT
.sp 1P
.LP
13.2.1.1.4\ \ \fIPresentation context definition list\fR
.sp 9p
.RT
.PP
The initiator of the association supplies the presentation context definition
list in the RT\(hyOPEN request primitive.
.PP
The presentation context definition list comprises a
presentation\(hycontext\(hydefinition for each abstract\(hysyntax included
in the
application\(hycontext. A presentation\(hycontext\(hydefinition comprises a
presentation\(hycontext\(hyidentifier and an abstract\(hysyntax\(hyname
for the ASE. The
named abstract\(hysyntax for the RTSE includes the abstract\(hysyntax for the
bind\(hyoperation.
.PP
Paragraph 12 defines the abstract\(hysyntaxes included in the
application\(hycontext.
.RT
.sp 1P
.LP
13.2.1.2\ \ \fIMTA\(hyunbind onto RT\(hyCLOSE\fR
.sp 9p
.RT
.PP
The MTA\(hyunbind is maped onto the RT\(hyCLOSE service of the RTSE.
.PP
No parameters of the RT\(hyCLOSE service are used in normal mode.
.RT
.sp 1P
.LP
13.2.2
\fIMapping onto RT\(hyTRANSFER\fR
.sp 9p
.RT
.PP
The message\(hytransfer, probe\(hytransfer and report\(hytransfer services
are mapped onto the RT\(hyTRANSFER service of the RTSE.
.PP
The mapping of these services onto the RT\(hyTRANSFER service in normal
mode is identical to the mapping in X.410\(hy1984 mode, defined in \(sc\
13.1.2.
.RT
.sp 1P
.LP
13.2.3
\fIManaging the turn\fR
.sp 9p
.RT
.PP
The MTSE must possess the turn before it can use the RT\(hyTRANSFER
service to transfer a message, probe or report.
.PP
Managing the turn in normal mode is identical to managing the turn in X.410\(hy1984
mode, defined in\ \(sc\ 13.1.3.
.RT
.sp 1P
.LP
13.2.4
\fIUse of the RT\(hyP\(hyABORT service\fR
.sp 9p
.RT
.PP
The application\(hyprocess is the user of the RT\(hyP\(hyABORT service of
the RTSE.
.PP
The RT\(hyP\(hyABORT service provides an indication to the
application\(hyprocess that the application\(hyassociation cannot be maintained
(e.g.\ because recovery not possible).
.PP
The RT\(hyP\(hyABORT service has no parameters.
.PP
Note that the use of the RT\(hyP\(hyABORT service in normal mode is
identical to the use of the RT\(hyP\(hyABORT service in X.410\(hy1984 mode.
.bp
.RT
.sp 1P
.LP
13.2.5
\fIUse of the RT\(hyU\(hyABORT service\fR
.sp 9p
.RT
.PP
The application\(hyprocess is the user of the RT\(hyU\(hyABORT service of
the RTSE.
.PP
The RT\(hyU\(hyABORT service enables the application\(hyprocess to abort the
application\(hyassociation. The RT\(hyU\(hyABORT service may be requested
by either the initiator or the responder of the association.
.PP
No parameters of the RT\(hyU\(hyABORT service are used in normal mode.
.PP
Note that the RT\(hyU\(hyABORT service is not available in X.410\(hy1984
mode.
.RT
.sp 2P
.LP
\fB14\fR \fBConformance\fR
.sp 1P
.RT
.PP
An MD claiming conformance to the MTS transfer protocol (P1)
specified in this Recommendation shall comply with the requirements in
\(sc\(sc\ 14.1, 14.2 and 14.3.
.RT
.sp 1P
.LP
14.1
\fIStatement requirements\fR
.sp 9p
.RT
.PP
The following shall be stated:
.RT
.LP
a)
the application\(hycontexts defined in Section 3 of this
Recommendation for which conformance is claimed;
.LP
b)
whether monologue, two\(hyway alternate, or both monologue and two\(hyway
alternate dialogue\(hymodes are supported;
.LP
c)
whether the MD can act as the initiator, or the responder, or either
the initiator or the responder, of an association.
.PP
Table 6/X.419 classifies the support for application\(hycontexts
required for conformance to the MTS transfer protocol (P1).
.ce
\fBH.T. [T6.419]\fR
.ce
TABLE\ 6/X.419
.ce
\fBMTS transfer protocol conformance requirements\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Application context MD
_
.T&
lw(90p) | lw(36p) .
T{
\fIMTS transfer protocol\fR
T}
.T&
lw(90p) | lw(36p) .
T{
mts\(hytransfer\(hyprotocol\(hy1984
T} Mandatory
.T&
lw(90p) | lw(36p) .
mts\(hytransfer\(hyprotocol Mandatory
.T&
lw(90p) | lw(36p) .
mts\(hytransfer Optional
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 6/X.419 [T6.419], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
14.2
\fIStatic requirements\fR
.sp 9p
.RT
.PP
The MD shall:
.RT
.LP
a)
conform to the abstract\(hysyntax definition of the MTS
transfer protocol (P1) defined in \(sc\ 12 of this Recommendation.
.sp 1P
.LP
14.3
\fIDynamic requirements\fR
.sp 9p
.RT
.PP
The MD shall:
.RT
.LP
a)
conform to the procedures for distributed operation of the MTS defined
in Recommendation\ X.411;
.LP
b)
conform to the mapping onto used services defined in \(sc\ 13 of this
Recommendation, required by the application\(hycontexts for which conformance
is claimed; support for the mapping onto the RTSE in X.410\(hy1984 mode
is
mandatory, and support for the mapping onto the RTSE in normal mode is
optional;
.LP
c)
conform to the rules for interworking with MDs conforming to Recommendation\
X.411 (1984) defined in Annex\ B of this Recommendation;
.LP
d)
conform to the use of underlying services defined in \(sc\ 11.3 of this
Recommendation.
.bp
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation X.419)
.sp 9p
.RT
.ce 0
.ce 1000
\fBReference definition of MHS protocol object identifiers\fR
.sp 1P
.RT
.ce 0
.PP
This Annex defines for reference purposes various object
identifiers cited in the ASN.1 modules in the body of this Recommendation.
The object identifiers are assigned in Figure\ 6/X.419.
.sp 1P
.RT
.PP
All object identifiers that this Recommendation assigns are
assigned in this Annex. However, this Annex is not definitive for all
assignments. Other definitive assignments occur in the modules in the body
of this Recommendation and are referred to in this Annex.
.LP
.sp 5
.LP
MHSProtocolObjectIdentifiers\|{\|joint\(hyiso\(hyccitt mhs\(hymotis(6)
protocols(0) modules(0) object\(hyidentifiers(0)\|}
.LP
DEFINITIONS IMPLICIT TAGS ::=
.LP
BEGIN
.LP
.sp 2
\(hy\(hy\ \fIPrologue\fR
.LP
\(hy\(hy\ \fIExports everything\fR
.LP
IMPORTS\ \(hy\(hy\ nothing \(hy\(hy ;
.LP
.sp 2
\(hy\(hy\ \fIMHS protocols\fR
.LP
id\(hymhs\(hyprotocols OBJECT IDENTIFIER ::=\|{\|joint\(hyiso\(hyccitt
mhs\(hymotis(6) protocols(0)\|}\|\(hy\(hy not definitive
.LP
.sp 2
.LP
\(hy\(hy\ \fICategories of object identifiers\fR
.LP
id\(hymod OBJECT IDENTIFIER ::=\|{\|id\(hymhs\(hyprotocols 0\|}
\(hy\(hy\ modules
.LP
id\(hyac OBJECT IDENTIFIER ::=\|{\|id\(hymhs\(hyprotocols 1\|}
\(hy\(hy\ application contexts
.LP
id\(hyas OBJECT IDENTIFIER ::=\|{\|id\(hymhs\(hyprotocols 2\|}
\(hy\(hy\ abstract syntaxes
.LP
id\(hyase OBJECT IDENTIFIER ::=\|{\|id\(hymhs\(hyprotocols 3\|}
\(hy\(hy\ application service elements
.LP
.sp 2
\(hy\(hy\ \fIModules\fR
.LP
id\(hymod\(hyobject\(hyidentifiers OBJECT IDENTIFIER ::=\|{\|id\(hymod 0\|}
\(hy\(hy\ not
definitive
.LP
id\(hymod\(hymts\(hyaccess\(hyprotocol OBJECT IDENTIFIER ::=\|{\|id\(hymod 1\|}
\(hy\(hy\ not
definitive
.LP
id\(hymod\(hyms\(hyaccess\(hyprotocol OBJECT IDENTIFIER::=\|{\|id\(hymod 2\|}
\(hy\(hy\ not
definitive
.LP
id\(hymod\(hymts\(hytransfer\(hyprotocol OBJECT IDENTIFIER ::=\|{\|id\(hymod
3\|}
\(hy\(hy\ not
definitive
.ce 1000
Figure\ 6/X.419\ (Part 1 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of MHS protocol object identifiers\fR
.ce 0
.sp 1P
.LP
.bp
.LP
\(hy\(hy\ \fIApplication contexts\fR
.LP
\(hy\(hy\ \fIMTS access protocol\fR
.LP
id\(hyac\(hymts\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac 0\|}
.LP
id\(hyac\(hymts\(hyforced\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac 1\|}
.LP
id\(hyac\(hymts\(hyreliable\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac 2\|}
.LP
id\(hyac\(hymts\(hyforced\(hyreliable\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac
3\|}
.LP
.sp 2
\(hy\(hy\ \fIMS access protocol\fR
.LP
id\(hyac\(hyms\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac 4\|}
.LP
id\(hyac\(hyms\(hyreliable\(hyaccess OBJECT IDENTIFIER ::=\|{\|id\(hyac 5\|}
.LP
.sp 2
\(hy\(hy\fIMTS transfer protocol\fR
.LP
id\(hyac\(hymts\(hytransfer OBJECT IDENTIFIER ::=\|{\|id\(hyac 6\|}
.LP
.sp 2
.LP
\(hy\(hy\ \fIAbstract syntaxes\fR
.LP
id\(hyas\(hyacse OBJECT IDENTIFIER ::=\|{\|joint\(hyiso\(hyccitt association\(hycontrol
(2) abstract\(hysyntax (1) opdus (0) version1\|(1)\|}
.LP
id\(hyas\(hymsse OBJECT IDENTIFIER ::=\|{\|id\(hyas 1\|}
.LP
id\(hyas\(hymdse OBJECT IDENTIFIER ::=\|{\|id\(hyas 2\|}
.LP
id\(hyas\(hymrse OBJECT IDENTIFIER ::=\|{\|id\(hyas 5\|}
.LP
id\(hyas\(hymase OBJECT IDENTIFIER ::=\|{\|id\(hyas 6\|}
.LP
id\(hyas\(hymtse OBJECT IDENTIFIER ::=\|{\|id\(hyas 7\|}
.LP
id\(hyas\(hymts\(hyrtse OBJECT IDENTIFIER ::=\|{\|id\(hyas 8\|}
.LP
id\(hyas\(hyms OBJECT IDENTIFIER ::=\|{\|id\(hyas 9\|)
.ce 1000
Figure\ 6/X.419\ (Part 2 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of MHS protocol object identifiers\fR
.ce 0
.sp 1P
.LP
.sp 1
.LP
id\(hyas\(hyms\(hyrtse OBJECT IDENTIFIER ::=\|{\|id\(hyas 10\|}
.LP
id\(hyas\(hymts OBJECT IDENTIFIER ::=\|{\|id\(hyas 11\|}
.LP
.sp 2
\(hy\(hy\ \fIApplication service elements\fR
.LP
id\(hyase\(hymsse OBJECT IDENTIFIER ::=\|{\|id\(hyase 0\|}
.LP
id\(hyase\(hymdse OBJECT IDENTIFIER ::=\|{\|id\(hyase 1\|}
.LP
id\(hyase\(hymrse OBJECT IDENTIFIER ::=\|{\|id\(hyase 2\|}
.LP
id\(hyase\(hymase OBJECT IDENTIFIER ::=\|{\|id\(hyase 3\|}
.LP
id\(hyase\(hymtse OBJECT IDENTIFIER ::=\|{\|id\(hyase 4\|}
.LP
.sp 2
END\
\(hy\(hy\ \fIof MHSProtocolObjectIdentifiers\fR
.ce 1000
Figure\ 6/X.419\ (Part 3 of 3)
.ce 0
.sp 1P
.ce 1000
\fBAbstract syntax definition of MHS protocol object identifiers\fR
.ce 0
.sp 1P
.LP
.bp
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation X.419)
.sp 9p
.RT
.ce 0
.ce 1000
\fBInterworking with 1984 systems\fR
.sp 1P
.RT
.ce 0
.PP
This Annex defines the rules to be obeyed by MDs claiming
conformance to this Recommendation (hereafter referred to as \*Q1988 systems\*U)
when interworking with implementations conforming to Recommendation\ X.411
(1984) (hereafter referred to as \*Q1984 systems\*U) using the MTS transfer
protocol (P1).
.sp 1P
.RT
.PP
Paragraph B.1 defines the rules for establishing associations that a 1988
system shall obey when interworking with a 1984 system.
.PP
Paragraph B.2 defines the rules that a 1988 system shall obey when
transferring an MTS\(hyAPDU to a 1984 system.
.PP
Paragraph B.3 defines the rules that a 1988 system shall obey when
receiving an MTS\(hyAPDU from a 1984 system.
.PP
\fINote\fR \ \(em\ As Recommendation\ X.411 (1984) only defines the interactions
at the boundary of an ADMD, the interworking rules in this Annex only apply
at such a boundary.
.PP
Additional types have been added to the universal class of ASN.1 types
compared to those defined in Recommendation\ X.409 (1984). The valid replacement
specifications for an ANY type are therefore extended. Note that 1984 systems
may be unable to handle the extended universal types. It is likely that
a 1984 system may correctly handle these fields even if they contain the
extended
types. However, such fields intended for a 1984 system should be restricted
to the universal types defined in Recommendation\ X.409 (1984).
.PP
The basic encoding rules for ASN.1 give more flexibility than
Recommendation\ X.409 (1984) for the long form of the length octets. The
former permits the use of more length octets than the minimum necessary,
whereas the latter does not. Therefore, when interworking with a 1984 system,
it is
necessary to obey this restriction, and use the fewest possible number of
octets, with no leading octets having the value\ 0.
.RT
.sp 1P
.LP
B.1
\fIAssociation establishment\fR
.sp 9p
.RT
.PP
This paragraph defines the restrictions that a 1988 system shall
observe with the MTA\(hybind when establishing an association with a 1984
system. There are no restrictions with the MTA\(hyunbind.
.PP
The \fBmts\(hytransfer\(hyprotocol\(hy1984\fR , as defined in \(sc\ 12,
shall be used
for compatibility with the 1984 system.
.RT
.sp 1P
.LP
B.1.1
\fIInitiator\(hycredentials/responder\(hycredentials\fR
.sp 9p
.RT
.PP
There are no restrictions placed on these elements as the
corresponding elements in Recommendation\ X.411 (1984) were each defined
to be ANY type. Note, however, that a 1984 system will be restricted in
its use of
these elements when interworking with 1988 systems as described above.
.RT
.sp 1P
.LP
B.1.2
\fISecurity\(hycontext\fR
.sp 9p
.RT
.PP
This optional element shall not be generated by a 1988 system when interworking
with a 1984 system. Note that a 1984 system is not capable of
generating this element.
.RT
.sp 1P
.LP
B.1.3
\fIBind\(hyerror\fR
.sp 9p
.RT
.PP
The bind\(hyerror value \fBunacceptable\(hysecurity\(hycontext\fR shall
not be generated by a 1988 system.
.bp
.RT
.sp 1P
.LP
B.2
\fIRules for transferring to 1984 systems\fR
.sp 9p
.RT
.PP
This paragraph defines the interworking rules that a 1988 system
shall obey when transferring an MTS\(hyAPDU to a 1984 system. The transformation
of an MTS\(hyAPDU conforming to Recommendation\ X.411 to one conforming
to
Recommendation\ X.411 (1984) is called \fIdowngrading\fR . The rules are
expressed in terms of the actions to be taken on each protocol element
of the MTS transfer protocol (P1) by the 1988 system.
.PP
For a given MTS\(hyAPDU, if none of the rules deem that downgrading would
fail, then the MTS\(hyAPDU shall be downgraded in accordance with all applicable
rules before being transferred to the 1984 system.
.PP
If one or more of the rules deem that downgrading has failed, then the
action taken by the MTA is the same as if the transfer had failed (see
\(sc\ 14
of Recommendation\ X.411).
.PP
\fINote\fR \ \(em\ The potential or actual loss of information caused by
applying these rules may affect an MTA's routing strategy.
.PP
The remainder of this paragraph specifies the rules for each of the
protocol elements. Protocol elements not specifically mentioned shall be
transferred unchanged. Unless otherwise specified, the rules specified
apply in whichever MTS\(hyAPDU the protocol elements appear.
.RT
.sp 1P
.LP
B.2.1
\fIExtensions\fR
.sp 9p
.RT
.PP
If any per\(hymessage \fBextensions\fR elements are present, and no
\fBextension\(hyfield\fR is marked \fBcritical\(hyfor\(hytransfer\fR or
\fBcritical\(hyfor\(hydelivery\fR , the \fBextensions\fR elements shall
be deleted.
.PP
If any per\(hymessage \fBextensions\fR elements are present, and any
\fBextension\(hyfield\fR is marked \fBcritical\(hyfor\(hytransfer\fR or
\fBcritical\(hyfor\(hydelivery\fR , downgrading shall fail.
.PP
These rules shall be applied before any of the rules described in the following
paragraphs.
.RT
.sp 1P
.LP
B.2.2
\fIPer\(hydomain\(hybilateral\(hyinformation\fR
.sp 9p
.RT
.PP
If a \fBprivate\(hydomain\(hyidentifier\fR is present in an element of
\fBper\(hydomain\(hybilateral\(hyinformation\fR , then that element of
\fBper\(hydomain\(hybilateral\(hyinformation\fR shall be deleted.
.PP
Otherwise, the \fBper\(hydomain\(hybilateral\(hyinformation\fR shall be
unchanged.
.RT
.sp 1P
.LP
B.2.3
\fITrace\(hyinformation/subject\(hyintermediate\(hytrace\(hyinformation\fR
.sp 9p
.RT
.PP
If an \fBother\(hyactions\fR element is present in any
\fBtrace\(hyinformation\(hyelements\fR or
\fBsubject\(hyintermediate\(hytrace\(hyinformation\(hyelements\fR , the
\fBother\(hyactions\fR element shall be deleted.
.PP
Otherwise, the \fBtrace\(hyinformation\fR or
\fBsubject\(hyintermediate\(hytrace\(hyinformation\fR shall be unchanged.
.RT
.sp 1P
.LP
B.2.4
\fIOriginator\(hyname/report\(hydestination\(hyname\fR
.sp 9p
.RT
.PP
If the \fBoriginator\(hyname\fR in a \fBmessage\(hytransfer\(hyenvelope\fR or a
\fBprobe\(hytransfer\(hyenvelope\fR , or if the \fBreport\(hydestination\(hyname\fR
in a
\fBreport\(hytransfer\(hyenvelope\fR , cannot be downgraded according to
the rules given for \fBOR\(hyname\fR (see \(sc\ B.2.7), then downgrading
shall fail.
.PP
Otherwise the element shall be unchanged.
.RT
.sp 1P
.LP
B.2.5
\fIPer\(hyrecipient\(hyfields of message\(hy or probe\(hytransfer\fR
.sp 9p
.RT
.PP
If a \fBrecipient\(hyname\fR in the \fBper\(hyreceipient\(hyfields\fR of a
\fBmessage\(hytransfer\(hyenvelope\fR or a \fBprobe\(hytransfer\(hyenvelope\fR
cannot be downgraded according to the rules given for \fBOR\(hyname\fR
(see \(sc\ B.2.7), or any
\fBper\(hyrecipient extension\(hyfield\fR exists and is marked \fBcritical\(hyfor\(hytransfer\fR
or \fBcritical\(hyfor\(hydelivery\fR , then:
.RT
.LP
a)
if the corresponding \fBresponsibility\fR element has the value \fBresponsible\fR
, then downgrading shall fail;
.LP
b)
if the corresponding \fBresponsibility\fR element has the value \fBnot\(hyresponsible\fR
, the the element for that recipient shall be deleted from
\fBper\(hyrecipient\(hyfields\fR .
.PP
\fINote\fR \ \(em\ The downgrading rules imply that
\fBdisclosure\(hyof\(hyrecipients\fR is neither critical\(hyfor\(hytransfer nor
critical\(hyfor\(hydelivery.
.bp
.sp 1P
.LP
B.2.6
\fIPer\(hyrecipient\(hyfields of report\(hytransfer\fR
.sp 9p
.RT
.PP
If an \fBactual\(hyrecipient\(hyname\fR or an \fBintended\(hyrecipient\(hyname\fR
in
the \fBper\(hyrecipient\(hyfields\fR of a \fBreport\(hytransfer\(hycontent\fR
cannot be downgraded according to the rules given for \fBOR\(hyname\fR
(see \(sc\ B.2.7), then the
corresponding element of \fBper\(hyrecipient\(hyfields\fR shall be deleted.
If all the
elements of \fBper\(hyrecipient\(hyfields\fR are so deleted,
down
grading shall fail.
.RT
.sp 1P
.LP
B.2.7
\fIOR\(hyname\fR
.sp 9p
.RT
.PP
The \fBOR\(hyname\fR shall be downgraded by deleting the \fBdirectory\(hyname\fR
, if present, and by downgrading the \fBOR\(hyaddress\fR (see \(sc\ B.2.8).
.RT
.sp 1P
.LP
B.2.8
\fIOR\(hyaddress\fR
.sp 9p
.RT
.PP
If the \fBOR\(hyaddress\fR contains any attributes encoded both as
teletext strings and as printable strings, the teletex strings shall be
deleted.
.PP
If the \fBOR\(hyaddress\fR is a \fBnumeric\(hyOR\(hyaddress\fR or a
\fBterminal\(hyOR\(hyaddress\fR containing a \fBprivate\(hydomain\(hyname\fR
, the \fBOR\(hyaddress\fR
cannot be downgraded.
.PP
If the \fBOR\(hyaddress\fR is a \fBtelematic\(hyOR\(hyaddress\fR :
.RT
.LP
a)
that contains a \fBcountry\(hyname\fR , an
\fBadministration\(hydomain\(hyname\fR , a \fBnetwork\(hyaddress\fR , optionally
\fBdomain\(hydefined\(hyattributes\fR , and no others, the \fBOR\(hyaddress\fR
shall be
unchanged;
.LP
b)
that contains a \fBnetwork\(hyaddress\fR , optionally a
\fBterminal\(hyidentifier\fR , and no others, the \fBOR\(hyaddress\fR shall
be unchanged;
.LP
c)
that contains combinations of attributes other than the
above, all attributes except the \fBnetwork\(hyaddress\fR and the \fBterminal\fR
\fBidentifier\fR , if present, shall be deleted.
.PP
If the \fBOR\(hyaddress\fR contains any attributes encoded as teletex
strings and the corresponding printable strings are absent, the \fBOR\(hyaddress\fR
cannot be downgraded.
.PP
If after applying all the above rules the \fBOR\(hyaddress\fR still contains
any \fBextension\(hyattributes\fR , the \fBOR\(hyaddress\fR cannot be downgraded.
.RT
.sp 1P
.LP
B.2.9
\fIEncoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
Basic \fBencoded\(hyinformation\(hytypes\fR indicated by object identifiers
shall be mapped to the corresponding bit in \fBbasic\(hyencoded\(hyinformation\(hytypes\fR
, and the object identifiers shall be deleted.
.PP
Other \fBencoded\(hyinformation\(hytypes\fR indicated by object identifiers
shall be mapped to the \fBundefined\fR bit in \fBbasic\(hyencoded\(hyinformation\(hytypes\fR
,
and the object identifiers shall be deleted.
.PP
Any \fBnon\(hybasic\(hyparameters\fR other than for \fBg4\(hyclass\(hy1\fR and
\fBmixed\(hymode\fR types shall not be altered. Those for \fBg4\(hyclass\(hy1\fR
and
\fBmixed\(hymode\fR may be transformed according to rules deduced from
Recommendations\ T.73 (1984), T.400, T.501 and T.503; if this is not possible,
downgrading shall fail.
.PP
Notwithstanding the above rules, \fBencoded\(hyinformation\(hytypes\fR in a
\fBreport\(hytransfer\(hycontent\fR shall be deleted.
.RT
.sp 1P
.LP
B.2.10\ \ \fIContent\(hytype and content\fR
.sp 9p
.RT
.PP
If the \fBcontent\(hytype\fR in a message or probe is indicated by
integer, it shall be unchanged. The \fBcontent\fR in the message shall also be
unchanged.
.PP
If the \fBcontent\(hytype\fR in a message is indicated by an object
identifier, it shall be mapped to the integer value \fBexternal\fR in place
of the object identifier. The object identifier and the \fBcontent\fR shall
be combined
together into a value of the EXTERNAL type, and this value shall be the
contents of the new \fBcontent\fR . The object identifier shall be the
EXTERNAL's
direct\(hyreference and the contents of the \fBcontent\fR OCTET STRING
shall be its
octet\(hyaligned encoding. The encoding of the \fBcontent\fR OCTET STRING
shall be the Basic Encoding Rules of ASN.1
.PP
If the \fBcontent\(hytype\fR in a probe is indicated by an object identifier,
downgrading shall fail.
.PP
The \fBcontent\(hytype\fR in a report shall be deleted. The
\fBreturned\(hycontent\fR shall be unchanged.
.bp
.RT
.sp 1P
.LP
B.3
\fIRules for receiving from 1984 systems\fR
.sp 9p
.RT
.PP
This paragraph defines the interworking rules which a 1988 system shall
obey upon receiving an MTS\(hyAPDU from a 1984 system.
.PP
Size constraints have been defined for a number of MTS transfer
protocol (P1) elements. Providing that a 1984 system observes these
constraints, a correctly encoded MTS\(hyAPDU received from a 1984\ sytem also
conforms to 1988\ MTS protocol (P1). Therefore, a 1988\ system need take no
special action.
.RT
.sp 1P
.LP
B.4
\fIService irregularities\fR
.sp 9p
.RT
.PP
The use of redirection and distribution lists in the presence of
1988/1984 domain boundaries may lead to some irregularities which are listed
below:
.RT
.LP
\(em
recipients may not be able to notice that they received
a message because of DL expansion or redirection;
.LP
\(em
when a message traverses a 1984 domain, the expansion history and the
redirection history are lost. This mat cause premature routing hop
detection and result in redirection or expansion failure. Note that only
a DL with a 1984 compatible O/R address may encounter this problem;
.LP
\fR \(em
1984 MTAs will return notifications to the message originator rather
than redirecting them back along the DL expansion path;
.LP
\(em
1984 systems may see new distinguished values for integer
protocol elements which are unknown to them.
\v'6p'
.ce 1000
ANNEX\ C
.ce 0
.ce 1000
(to Recommendation X.419)
.sp 9p
.RT
.ce 0
.ce 1000
\fBDifferences between 1984 and 1988 MHS protocols\fR
.sp 1P
.RT
.ce 0
.PP
\fR
This Annex identifies the differences between the MTS access
protocol (P3) and MTS transfer protocol\ (P1) defined in this Recommendation
and the\ P3 and P1\ protocols defined in Recommendation\ X.411\ (1984).
Differences of a purely editorial nature are not included here.
.sp 1P
.RT
.PP
The differences are identified in terms of the additions or other changes
made to protocol elements present in\ P3 and\ P1 are defined in
Recommendation\ X.411\ (1984). The differences are more precisely indicated in
the abstract syntax definitions in Recommendation\ X.411, in which every data
type that has been changed is highlighted by means of
underlining
.
.PP
Paragraph C.1 identifies the differences in the MTS access protocol
(P3). Paragraph\ C.2 identifies the additional differences in the MTS transfer
protocol\ (P1).
.RT
.sp 1P
.LP
C.1
\fIMTS access protocol (P3) differences\fR
.sp 9p
.RT
.PP
This paragraph identifies the differences between the MTS access
protocol\ (P3) defined in this Recommendation and the P3\ protocol defined in
Recommendation\ X.411\ (1984).
.RT
.sp 1P
.LP
C.1.1
\fISize constraints\fR
.sp 9p
.RT
.PP
Constraints to limit the length of string types, the number of
items in a SET OF or SEQUENCE OF type, and the value range of INTEGER types
have been placed on all parameters defined in Recommendation\ X.411 (1984)
with the exception of the message \fBcontent\fR .
.RT
.sp 1P
.LP
C.1.2
\fIChanges to fundamental types\fR
.sp 9p
.RT
.PP
The parameters \fBOR\(hyname\fR , \fBcontent\(hytype\fR ,
\fBencoded\(hyinformation\(hytypes\fR and \fBcontent\fR , which occur in
various places in the operation arguments and results, have been extended,
as described below.
.bp
.RT
.sp 1P
.LP
C.1.2.1\ \ \fIOR\(hyname\fR
.sp 9p
.RT
.PP
Two new optional parameters have been added to \fBOR\(hyname\fR .
.PP
\fR The first of these is a set of \fBextension\(hyattributes\fR that provide
the means of using the teletex character set for the \fBstandard\(hy\fR and
\fBdomain\(hydefined\(hyattributes\fR , of specifying a \fBpostal\(hyOR\(hyaddress\fR
for physical delivery, and of specifying a \fBterminal\(hyaddress\fR from
an
\fBextended\(hynetwork\(hyaddress\fR .
.PP
The second of these is a \fBdirectory\(hyname\fR , as defined in
Recommendation\ X.501.
.PP
If only \fBstandard\(hy, \fBdomain\(hydefined\(hy\fR or \fBextension\(hyattributes\fR
are \fR present, then the \fBOR\(hyname\fR constitutes an \fBOR\(hyaddress\fR
. Otherwise, a
\fBdirectory\(hyname\fR is also present. If a \fBdirectory\(hyname\fR alone
is present, it
may be necessary to map the \fBdirectory\(hyname\fR to an \fBOR\(hyaddress\fR
(e.g.,\ using
the directory).
.RT
.sp 1P
.LP
C.1.2.2\ \ \fIContent\(hytype\fR
.sp 9p
.RT
.PP
The option of identifying the \fBcontent\(hytype\fR with an object
ifentifier instead of an integer has been added. It is the preferred method
of identifying new \fBcontent\(hytypes\fR , and the assignment of new integer
values is discouraged. Three new values have been defined for the integer
choice:
\fBundefined, external\fR and \fBinterpersonal\(hymessaging\(hy1988\fR .
.RT
.LP
\fR
.sp 1P
.LP
C.1.2.3\ \ \fIEncoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
The option of specifying a set of external
\fBencoded\(hyinformation\(hytypes\fR has been added. All new \fBencoded\(hyinformation\(hytypes\fR
will be added as an object identified.
.PP
The definition of the \fBnon\(hybasic\(hyparameters\fR for the \fBg4\(hyclass\(hy1\fR
and \fBmixed\(hymode\fR types has been amended in that the definition referenced
in
Recommendations\ T.400, T.501 and\ T.503 has changed from that previously
referenced in Recommendation\ T.73\ (1984), and in that it now uses explicit
instead of implicit tagging.
.RT
.sp 1P
.LP
C.1.2.4\ \ \fIContent\fR
.sp 9p
.RT
.PP
The \fBcontent\fR of a message is still of type OCTET STRING. If the
\fBcontent\(hytype\fR is identified by the integer value \fBexternal\fR
, the \fBcontent\fR is termed an \fBexternal\(hycontent\fR . The value
of the OCTET STRING for an
\fBexternal\(hycontent\fR shall be the ASN.1 encoding of an EXTERNAL.
.RT
.sp 1P
.LP
C.1.3
\fIExtensions\fR
.sp 9p
.RT
.PP
Most of the extensions to the MTS abstract service definied in
Recommendation\ X.411 are accomodated in the protocol by the addition of a
single new parameter \fBextensions\fR into the operation envelopes and results.
The parameter is absent when no extensions are required. It may be present
in the:
.RT
.LP
\(em
\fBMessage\(hysubmission\(hyenvelope\fR , on a per\(hymessage and
per\(hyrecipient basis;
.LP
\(em
\fBMessage\(hysubmission\(hyresult\fR ;
.LP
\(em
\fBProbe\(hysubmission\(hyenvelope\fR , on a per\(hyprobe and per\(hyrecipient
basis;
.LP
\(em
\fBProbe\(hysubmission\(hyresult\fR ;
.LP
\(em
\fBMessage\(hydelivery\(hyenvelope\fR ; and
.LP
\(em
\fBReport\(hydelivery\(hyenvelope\fR , on a per\(hyreport and per\(hyrecipient
basis.
.sp 1P
.LP
C.1.4
\fIBind\fR
.sp 9p
.RT
.PP
In Recommendation X.411 (1984), credentials of type ANY are
exchanged using the bind argument and result. The type of the ANY is
restricted in this Recommendation to a choice of \fBsimple\(hycredentials\fR
(either an IA5String or an OCTET STRING), or \fBstrong\(hycredentials\fR
based on
cryptographic techniques.
.PP
An optional parameter to specify a \fBsecurity\(hycontext\fR has been added
to the argument. A new error has been added to indicate an
\fBunacceptable\(hysecurity\(hycontext\fR .
.RT
.sp 1P
.LP
C.1.5
\fIMessage\(hysubmission\fR
.sp 9p
.RT
.PP
The \fBoriginal\(hyencoded\(hyinformation\(hytypes\fR and \fBexplicit\(hyconversion\fR
parameters in the \fBmessage\(hysubmission\(hy
\fBenvelope\fR have been made optional.
.PP
Two new errors have been added: \fBinconsistent\(hyrequest\fR and
\fBsecurity\(hyerror\fR .
.bp
.RT
.sp 1P
.LP
C.1.6
\fIProbe\(hysubmission\fR
.sp 9p
.RT
.PP
As for message\(hysubmission, see \(sc\ C.1.5.
.RT
.sp 1P
.LP
C.1.7
\fICancel\(hydeferred\(hydelivery\fR
.sp 9p
.RT
.PP
This operation is virtually unchanged with the exception of the
size constraints described in \(sc\ C.1.1 and the removal of the message
transferred error (subsumed by deferred\(hydelivery\(hycancellation\(hyrejected).
.RT
.sp 1P
.LP
C.1.8
\fISubmission\(hycontrol\fR
.sp 9p
.RT
.PP
An optional parameter \fBpermissible\(hysecurity\(hycontext\fR has been
added to the argument.
.PP
An optional parameter \fBwaiting\(hycontext\(hytypes\fR has been added to the
result to specify the \fBcontent\(hytypes\fR of any waiting messages held
due to
prevailing controls. The indicator \fBother\(hysecurity\(hylabels\fR has
been added to
the \fBwaiting\(hymessages\fR parameter of the result.
.PP
An error has been added: \fBsecurity\(hyerror\fR .
.RT
.sp 1P
.LP
C.1.9
\fIMessage\(hydelivery\fR
.sp 9p
.RT
.PP
The \fBoriginal\(hyencoded\(hyinformation\(hytypes\fR and \fBdelivery\(hyflags\fR
parameters have been made optional in the \fBmessage\(hydelivery\(hyenvelope\fR
, and an optional parameter \fBcontent\(hyidentifier\fR has been added
to it.
.PP
The operation has been made confirmed by adding a RESULT clause,
which contains two optional security parameters: \fBrecipient\(hycertificate\fR
and
\fBproof\(hyof\(hydelivery\fR .
.PP
One new error has been added: \fBsecurity\(hyerror\fR .
.RT
.sp 1P
.LP
C.1.10\ \ \fIReport\(hydelivery\fR
.sp 9p
.RT
.PP
Two new optional parameters have been added to the
\fBreport\(hydelivery\(hyenvelope\fR : the \fBcontent\(hytype\fR and the
\fBoriginal\(hyencoded\(hyinformation\(hytypes\fR of the original message.
.PP
Five new \fBnon\(hydelivery\(hyreason\(hycodes\fR and 35 new
\fBnon\(hydelivery\(hydiagnostic\(hycodes\fR have been defined.
.PP
Five new values of the \fBtype\(hyof\(hyMTS\(hyuser\fR parameter have\fR
been added: \fBmessage\(hystore\fR , \fBdistribution\(hylist\fR , \fBphysical\(hydelivery\(hyaccess\(hyunit\fR
,
\fBphysical\(hyrecipient\fR and \fBother\fR .
.PP
The operation has been made confirmed by adding a RESULT clause
(which conveys no parameters).
.PP
One new error has been added: \fBsecurity\(hyerror\fR .
.RT
.sp 1P
.LP
C.1.11\ \ \fIDelivery\(hycontrol\fR
.sp 9p
.RT
.PP
Two new optional control parameters have been added to the
argument: \fBpermissible\(hycontent\(hytypes\fR and \fBpermissible\(hysecurity\(hycontext\fR
.
.PP
An optional \fBwaiting\(hycontent\(hytypes\fR parameter has been added to the
result.
.PP
Two new errors have been added: \fBcontrol\(hyviolates\(hyregistration\fR and
\fBsecurity\(hyerror\fR .
.RT
.sp 1P
.LP
C.1.12\ \ \fIRegister\fR
.sp 9p
.RT
.PP
Two new optional parameters have been added to the argument:
\fBdeliverable\(hycontent\(hytypes\fR and \fBlabels\(hyand\(hyredirections\fR .
.PP
The tags on the restrict, \fBpermissible\(hyoperations\fR and
\fBpermissible\(hymaximum\(hycontent\(hylength\fR parameters of the
\fBdefault\(hydelivery\(hycontrols\fR have been altered. The \fBpermissible\(hycontent\(hytypes\fR
parameter has been added.
.RT
.sp 1P
.LP
C.1.13\ \ \fIChange\(hycredentials\fR
.sp 9p
.RT
.PP
This possible types supplied fot the credentials in this operation have
been restricted, as described in\ \(sc\ C.1.4. The relationship between
the
types supplied for the \fBold\(hycredentials\fR and \fBnew\(hycredentials\fR
has also been
restricted (to be of the same type).
.bp
.RT
.sp 1P
.LP
C.2
\fIMTS transfer protocol (P1) differences\fR
.sp 9p
.RT
.PP
This paragraph identifies the differences between the MTS transfer protocol
(P1) defined in this Recommendation and the P1 protocol defined
in Recommendation\ X.411\ (1984).
.PP
The following changes to the MTS transfer protocol (P1) are the same as
those defined for the MTS access protocol (P3): size constraints (see
\(sc\ C.1.1), changes to fundamental types (see \(sc\ C.1.2) and bind
(see\ \(sc\ C.1.4).
.PP
The following paragraphs detail other changes to the MTS transfer
protocol (P1).
.RT
.sp 1P
.LP
C.2.1
\fIExternal\(hyfields\fR
.sp 9p
.RT
.PP
The new parameter \fBextensions\fR is used to include most of the
abstract\(hyservice extensions to the MTS transfer protocol (P1) (see \(sc\
C.1.3).
The parameter is absent when no extensions are required. It may be present
in the:
.RT
.LP
\(em
\fBMessage\(hytransfer\(hyenvelope\fR , on a per\(hymessage and
per\(hyrecipient basis.
.LP
\(em
\fBProbe\(hytransfer\(hyenvelope\fR , on a per\(hyprobe and per\(hyrecipient
basis.
.LP
\(em
\fBReport\(hytransfer\(hyenvelope\fR .
.LP
\(em
\fBReport\(hytransfer\(hycontent\fR , on a per\(hyreport and per\(hyrecipient
basis.
.sp 1P
.LP
C.2.2
\fIOthers differences\fR
.sp 9p
.RT
.PP
Two optional parameters have been added to the per\(hyreport transfer fields
of the \fBreport\(hytransfer\(hyenvelope\fR : \fBoriginal\(hyencoded\(hyinformation\(hytypes\fR
and \fBcontent\(hytype\fR .
.PP
An optional \fBprivate\(hydomain\(hyidentifier\fR has been added to the
\fBper\(hydomain\(hybilateral\(hyinformation\fR parameter of the message\(hy
and
\fBprobe\(hytransfer\(hyenvelopes\fR . This permits \fBper\(hydomain\(hybilateral\(hyinformation\fR
to be sent to PRMDs as well as ADMDs.
.PP
An optional \fBother\(hyactions\fR parameter has been added to the elements
of \fBtrace\(hyinformation\fR . The new parameter conveys two flags: \fBredirected\fR
to
indicate that the message was redirected by that MD, and \fBexpanded\fR
to indicate that the MD expanded a distribution\(hylist.
\v'6p'
.RT
.ce 1000
ANNEX\ D
.ce 0
.ce 1000
(to Recommendation X.419)
.sp 9p
.RT
.ce 0
.ce 1000
\fBDifferences between ISO and CCITT versions\fR
.sp 1P
.RT
.ce 0
.PP
This Annex identifies the technical differences between the ISO
and CCITT versions of the text of CCITT Recommendations\ X.419 and ISO\
10021\(hy6 as they relate to the support of the MTS transfer protocol (P1).
.sp 1P
.RT
.PP
They are:
.LP
1)
In CCITT Recommendation X.419, it is a mandatory conformance requirement
to have the capability to interwork with implementations of the
CCITT Recommendation\ X.411 (1984) using the MTS Transfer Protocol (P1) (for
ADMD \(hy ADMD and ADMD \(hy PRMD). In ISO\ 10021\(hy6, the capability
to interwork with 1984 systems is optional (for PRMD \(hy PRMD and intra\(hydomain).
.LP
2)
In CCITT Recommendation X.419, support for the mapping of
the MTS transfer protocol (P1) onto the RTSE in X.410\(hy1984 mode is a
mandatory conformance requirement; support for the mapping onto the RTSE
in normal mode is optional. In ISO\ 10021\(hy6, support for the mapping
onto the RTSE in normal
mode is mandatory, support for the mapping onto the RTSE in X.410\(hy1984
mode is optional.
.LP
\fINote\fR \ \(em\ An implementation conformant only to the mandatory
mapping of ISO\ 10021\(hy6 would not be capable of interworking with
implementations of the CCITT Recommendation\ X.411 (1984), nor implementations
conformant only to the mandatory mapping of CCITT Recommendation\ X.419
(1988), and vice versa.
.LP
3)
In CCITT Recommendation X.419, requirements are made for the support
of lower layer services (see\ \(sc\ 11.3.4). In ISO\ 10021\(hy6, these
requirements are omitted.
.LP
.bp